Re: [fpc-devel] C-block reference syntax (blocker for 3.2)

2019-12-07 Thread Blaise
On 07.12.2019 21:39, Sven Barth wrote: I'm arguing that there is no builtin way to *access* the parameters passed in such a way. You are arguing that /now/, but it is not what you said earlier. You said, verbatim: one can not access VarArgs parameters inside a Delphi function (without

Re: [fpc-devel] C-block reference syntax (blocker for 3.2)

2019-12-07 Thread Sven Barth via fpc-devel
Am 07.12.2019 um 14:31 schrieb bla...@blaise.ru: your argument with VarArgs does not count either: one can not access VarArgs parameters inside a Delphi function (without resorting to assembly) Again, you are misinformed. I understand that you may not use DCC as much or at all, but you have

[fpc-devel] Cross-linking a DLL

2019-12-07 Thread Alfred
Dear All, Looking at t_linux.pas, this code is common (also for other system files): if (isdll) then begin Add('INPUT('); Add(sysrootpath+info.DynamicLinker); Add(')'); end; And also: if libraryadded and not(linklibc) and not(isdll) and (tf_section_threadvars in

Re: [fpc-devel] C-block reference syntax (blocker for 3.2)

2019-12-07 Thread Blaise
On 07.12.2019 14:21, Sven Barth wrote: I stand by my point that the combination of anonymous function variables with calling conventions and cblocks occurs very, very seldomly. I am not necessarily disputing that point, I am disputing your design decision, which was misinformed, but you

Re: [fpc-devel] C-block reference syntax (blocker for 3.2)

2019-12-07 Thread Michael Van Canneyt
On Sat, 7 Dec 2019, Sven Barth via fpc-devel wrote: Am 07.12.2019 um 10:28 schrieb Jonas Maebe: If there is a consensus that this is a blocker, I am ready to do the work ASAP. provided we select the syntax. Personally, I am inclined towards these three: type M = procedure (const N:

Re: [fpc-devel] C-block reference syntax (blocker for 3.2)

2019-12-07 Thread Sven Barth via fpc-devel
Am 07.12.2019 um 10:28 schrieb Jonas Maebe: If there is a consensus that this is a blocker, I am ready to do the work ASAP. provided we select the syntax. Personally, I am inclined towards these three: type M = procedure (const N: Integer) with var; type M = procedure (const N:

Re: [fpc-devel] C-block reference syntax (blocker for 3.2)

2019-12-07 Thread Sven Barth via fpc-devel
Am 07.12.2019 um 01:00 schrieb bla...@blaise.ru: Beforehand, to provide a context, here are some excerpts from private correspondence: On 11.12.2016 22:00:37 +0300, bla...@blaise.ru wrote in 1c51a35a-bbbc-c99d-232f-0bf6529df...@blaise.ru: my progress thus far 9) Method reference directives

Re: [fpc-devel] C-block reference syntax (blocker for 3.2)

2019-12-07 Thread Jonas Maebe
On 2019-12-07 01:00, bla...@blaise.ru wrote: 3) My first example back in 2016 intentionally featured a valid use case: CDECL is crucial for VARARGS. (Somehow, not only that case, but the whole point that DCC accepts calling conventions went unnoticed.) I indeed did not know that. I wonder

Re: [fpc-devel] C-block reference syntax (blocker for 3.2)

2019-12-07 Thread Michael Van Canneyt
On Sat, 7 Dec 2019, bla...@blaise.ru wrote: Beforehand, to provide a context, here are some excerpts from private correspondence: If there is a consensus that this is a blocker, I am ready to do the work ASAP. provided we select the syntax. Personally, I am inclined towards these three: