[fpc-devel] Request to merge revision 19247 to fixes branch (2.6)

2011-09-26 Thread Luiz Americo Pereira Camara
In the cited revision i fixed a bug in Sqlite*Dataset that can cause data corruption in some circumstances Luiz ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel

Re: [fpc-devel] New FPC Target: AROS

2011-09-26 Thread Sven Barth
Am 26.09.2011 15:45, schrieb Michael Schnell: On 09/26/2011 03:21 PM, Sven Barth wrote: Pre-4.x versions of AmigaOS supported 68k, newer ones support only PowerPC. Also AROS seems to be mainly based on x86 and PowerPC (a port to 68k exists though). So 68k does not seem to be necessary. So I se

Re: [fpc-devel] New FPC Target: AROS

2011-09-26 Thread Michael Schnell
On 09/26/2011 03:21 PM, Sven Barth wrote: Pre-4.x versions of AmigaOS supported 68k, newer ones support only PowerPC. Also AROS seems to be mainly based on x86 and PowerPC (a port to 68k exists though). So 68k does not seem to be necessary. So I seem to be out of luck :( :) -Michael ___

Re: [fpc-devel] New FPC Target: AROS

2011-09-26 Thread Sven Barth
Am 26.09.2011 14:29, schrieb Michael Schnell: I understand that for Amiga you need an 68 K (cross compiler) version of FPC. Pre-4.x versions of AmigaOS supported 68k, newer ones support only PowerPC. Also AROS seems to be mainly based on x86 and PowerPC (a port to 68k exists though). So 68k d

Re: [fpc-devel] New FPC Target: AROS

2011-09-26 Thread Michael Schnell
On 08/05/2011 09:47 PM, Marcus Sackrow wrote: ... Hi Marcus,. Any progress ? I understand that for Amiga you need an 68 K (cross compiler) version of FPC. I'd be interested in same, as well. Any progress here? ___ fpc-devel maillist - fpc-dev

Re: [fpc-devel] Major problem with Move and Array of Int64

2011-09-26 Thread LacaK
Martin Schreiber wrote / napĂ­sal(a): On Friday 23 September 2011 14.00:07 Sergei Gorelkin wrote: Recently strings behavior was changed, they are now codepage-aware. The compiler can now implicitly convert strings from one encoding to another. To handle non-string data, you should use RawByte