[fpc-devel] Using Macros for IInterface

Sven Barth pascaldragon at googlemail.com
Wed Sep 26 13:48:25 CEST 2012

Am 26.09.2012 12:37, schrieb michael.vancanneyt at wisa.be:
>>>> My suggestions (if we do indeed enable it):
>>>> intfconst for constref/const
>>>> intfdecl for stdcall/cdecl {I would not use extdecl so that there
>>>> are no
>>>> potential conflicts}
>>> libcall was already mentioned. It also helps in a lot of other
>>> places, and
>>> kills ninetynine percent of macro use. (which IMHO is always a good
>>> thing)
>> The question is then whether this should indeed be a new calling
>> convention or merely something that translates to stdcall/cdecl...
> I would be in favour of handling it at the level of the parser, but
> simply translate to cdecl/stdcall. I would not use a macro that is
> handled on the level of the scanner.
> The parser has more info at it's disposal, which could be useful if the
> behaviour needs to be refined.

Of course I would do it at the level of the parser. Otherwise we could 
just have used macros ;)


More information about the fpc-devel mailing list