[fpc-pascal] fpc 3.0 ansistring codepage behavior

I am debugging an issue (x86_64 Linux platform) which I have in FPC 3.0 which I didn't have in 2.6.4. It is a complex project with a lot of threading, custom memory management, etc., so it's not something I can easily boil down at the moment. Generally it manifests itself in memory corruption. As

Re: [fpc-pascal] Access violation in an empty project declaring heaptrc

On Thu, Mar 3, 2016 at 4:05 AM, Sven Barth wrote: [...] > That is the memory that had been used before the memory manager of the > heaptrc unit had been setup. Remember that there's first the System unit > initialization and only then the initialization of the

Re: [fpc-pascal] Primitive Record Wrappers

On Thu, Mar 3, 2016 at 10:16 AM, Mazola Winstrol wrote: > 2016-03-02 23:12 GMT-03:00 silvioprog : > >> On Tue, Mar 1, 2016 at 12:08 AM, Mazola Winstrol >> wrote: >> [...] >>> >>> I apologize, it works. >>> >> >> Do you have plan

Re: [fpc-pascal] Primitive Record Wrappers

2016-03-02 23:12 GMT-03:00 silvioprog : > On Tue, Mar 1, 2016 at 12:08 AM, Mazola Winstrol > wrote: > [...] >> >> I apologize, it works. >> > > Do you have plan to share it in some place like Github, Lazarus-CCR or as > Lazarus generics demo? Just a

Re: [fpc-pascal] Happy tickets benchmark

Jonas Maebe-2 wrote > On the contrary, it is fundamental. Changing defaults in existing > language modes, or changing the default language mode that is used, > would break existing code with as only reason that we wouldn't want to > look bad when people use the compiler for the first time

Re: [fpc-pascal] compile Link Smart option, is it -XX or -CX?

On Thu, March 3, 2016 12:12, Dennis Poon wrote: > Sven Barth wrote: >> Am 03.03.2016 09:26 schrieb "Dennis" > >: >> > >> > According to http://www.freepascal.org/docs-html/prog/progse30.html >> > >> > the smartlink option on the command line is

Re: [fpc-pascal] compile Link Smart option, is it -XX or -CX?

Sven Barth wrote: Am 03.03.2016 09:26 schrieb "Dennis" >: > > According to http://www.freepascal.org/docs-html/prog/progse30.html > > the smartlink option on the command line is -CX > but in Lazarus ver 1.42, >Compilation and Linking

Re: [fpc-pascal] Happy tickets benchmark

Serguei TARASSOV wrote on Thu, 03 Mar 2016: If I understood correctly, the FPC programmer in 2016 always should include {$MODE DELPHI} or {$MODE ObjFPC} to avoid TurboPascal legacy that I use in earlies 1990? FPC mode started in those same early 1990s. The first code that was written for

Re: [fpc-pascal] Happy tickets benchmark

Jonas Maebe-2 wrote > The reason is, as always, compatibility. FPC mode started as an > extension of the Turbo Pascal compatibility mode. In Turbo Pascal, > integer is 16 bits. In Delphi, it's 32 bits, so both in Delphi and in > ObjFPC modes, integer is 32 bits. Code that was written with

Re: [fpc-pascal] compile Link Smart option, is it -XX or -CX?

Am 03.03.2016 09:26 schrieb "Dennis" : > > According to http://www.freepascal.org/docs-html/prog/progse30.html > > the smartlink option on the command line is -CX > but in Lazarus ver 1.42, >Compilation and Linking > Linking > Link Smart is -XX They are

Re: [fpc-pascal] Happy tickets benchmark

Serguei TARASSOV wrote on Thu, 03 Mar 2016: Jeppe Johansen-3 wrote The Integer type depends on what compiler mode you are in, and what operating system. Sometimes it's 32bit and other times it's 16bit. AFAIK it only depends on the compiler mode. It was FPC 2.6.4 64 bits in FPC mode on

Re: [fpc-pascal] Happy tickets benchmark

Jeppe Johansen-3 wrote > On 03/02/2016 12:48 AM, vfclists . wrote: >> >> >> On 14 February 2016 at 10:06, Serguei TARASSOV > serge@ > > mailto: > serge@ > > wrote: >> Another strange effect in FPC. >> Only longint shows correct result. With the integer type the >> optimizer