On 20/03/2025 22:38, Marco van de Voort via fpc-devel wrote:
Op 20-3-2025 om 20:46 schreef Martin Frb via fpc-devel:
So why does the compiler interpret NoStackFrame in the type
declaration, when it does not do that for other non-relevant
modifiers (like assembler)?
I think it is because nos
Op 20-3-2025 om 20:46 schreef Martin Frb via fpc-devel:
So why does the compiler interpret NoStackFrame in the type
declaration, when it does not do that for other non-relevant modifiers
(like assembler)?
I think it is because nostackframe is a directive for the declaration of
the function
Ok, maybe I lost the point in verbosity.
The following type
type a=procedure foo;
gives the error
project1.lpr(2,19) Fatal: Syntax error, ";" expected but
"identifier FOO" found
In a type declaration, the procedure can not have a name, and "foo" is
not a valid modifier here (cdecl wou
Op 20-3-2025 om 20:09 schreef Martin Frb via fpc-devel:
It is possible to declare a type for a cdecl function like
type a=procedure cdecl;
But, not for "assembler" which makes sense, because its not a calling
convention. Same should likely be the case for NoStackframe.
Roughly yes. Basicall
