Re: [fpc-pascal] SIGSEGV when using varargs calling

2016-01-24 Thread Sven Barth
Am 25.01.2016 04:42 schrieb "silvioprog" : > What I'm doing wrong? Can I use this callings on FPC in the DELPHI mode?! :-/ Neither FPC nor Delphi allow you to declare your own varargs functions. That it works in Delphi is by pure change. Trying to outsmart the compiler will only lead to trouble.

[fpc-pascal] SIGSEGV when using varargs calling

2016-01-24 Thread silvioprog
Hello, Consider the following types: TPuts1 = procedure; cdecl varargs; TPuts2 = procedure(par: string); cdecl varargs; TPuts3 = procedure(const par: string); cdecl varargs; this procedure: procedure Puts(par1, par2, par3: string); cdecl; begin Write(par1, ' '); Write(par2, '

Re: [fpc-pascal] CrossFPC

2016-01-24 Thread Andreas
I tried it with XE6 since it said it should work with versions above XE4. Guess I was wrong. Will try it with XE3 which I also have. Thanks. On Sun 24/01/2016 13:23, Michael Ring wrote: What version of Delphi do you use? CrossFPC is compatible to only rather 'old' Versions, the documentation

Re: [fpc-pascal] CrossFPC

2016-01-24 Thread Michael Ring
What version of Delphi do you use? CrossFPC is compatible to only rather 'old' Versions, the documentation on main page says XE4. I was subscribed to the Mailinglist but have not received a single mail for the last years so propably the mailinglist is dead. Michael Am 24.01.16 um 16:03 sch

[fpc-pascal] CrossFPC

2016-01-24 Thread Andreas
CrossFPC recently released a new update and I decided to test it. Howerver it fails to install on either of my two machine. I tried subscribing the their email list (twice) but with no success. I never received the confirmation email. I know this is not the CrossFPC list, and most on this list

Re: [fpc-pascal] AVR Busy Wait implementation

2016-01-24 Thread Florian Klämpfl
Am 24.01.2016 um 00:00 schrieb Simon Ameis: > Would it be possible to issue a hint why a procedure can't be inlined at > a specific call? > This could change with the compiler and the user knows what to change > for inlining. The compiler tries to do this as debug info (-vd), see also fpc/compile