[fpc-devel] fpc modifiers

2011-04-28 Thread Joerg Schuelke
First i will note that what i state is not an error or bug in free pascal, but it is somehow unclean implemented. The decision for modifiers like cvar or cdecl to be an identifier token or an modifier token relies on context information. But what is that context? An example: type

[fpc-devel] __LINE__ and __FILE__ macros

2011-04-28 Thread Joerg Schuelke
Best regards to all developers, is it somehow possible to access the line number and file information during the compilation? This would be nice for debugging purposes. I do not write about the compiled in debug information for gdb. ASSERT can - i read it in the documentation - access this

Re: [fpc-devel] fpc modifiers

2011-04-28 Thread Marco van de Voort
In our previous episode, Joerg Schuelke said: [ Charset UTF-8 unsupported, converting... ] First i will note that what i state is not an error or bug in free pascal, but it is somehow unclean implemented. The decision for modifiers like cvar or cdecl to be an identifier token or an modifier

Re: [fpc-devel] __LINE__ and __FILE__ macros

2011-04-28 Thread Marco van de Voort
In our previous episode, Joerg Schuelke said: Best regards to all developers, is it somehow possible to access the line number and file information during the compilation? This would be nice for debugging purposes. Look in the manual under preprocessor $i (include)

Re: [fpc-devel] __LINE__ and __FILE__ macros

2011-04-28 Thread Joerg Schuelke
Am Thu, 28 Apr 2011 18:23:10 +0200 (CEST) schrieb mar...@stack.nl (Marco van de Voort): Look in the manual under preprocessor $i (include) thx, hard to find there. I thought i did read them all, but ... ___ fpc-devel maillist -

Re: [fpc-devel] fpc modifiers

2011-04-28 Thread Joerg Schuelke
Am Thu, 28 Apr 2011 18:22:38 +0200 (CEST) schrieb mar...@stack.nl (Marco van de Voort): In our previous episode, Marco van de Voort said: No, since modifiers can be in any order, it could be a lot more than two tokens. I think if the compiler reeds the cdecl token he needs a lookup of only

Re: [fpc-devel] __LINE__ and __FILE__ macros

2011-04-28 Thread Joerg Schuelke
Am Thu, 28 Apr 2011 18:23:10 +0200 (CEST) schrieb mar...@stack.nl (Marco van de Voort): Look in the manual under preprocessor $i (include) Thats better then nothing, but if you want to include this information in debugging information, and you won't write it again and again you will need an

Re: [fpc-devel] __LINE__ and __FILE__ macros

2011-04-28 Thread Joerg Schuelke
Am Thu, 28 Apr 2011 20:09:59 +0200 schrieb Joerg Schuelke joerg.schue...@gmx.de: No further explanation needed. Nested comments do it. I did not know that {$define mx:= ... (*$%LINE%*)} works. Best regards to Marco Jörg ___ fpc-devel maillist

Re: [fpc-devel] fpc modifiers

2011-04-28 Thread Hans-Peter Diettrich
Joerg Schuelke schrieb: First i will note that what i state is not an error or bug in free pascal, but it is somehow unclean implemented. The bug resides in the dirty Delphi OPL definition. DoDi ___ fpc-devel maillist -

Re: [fpc-devel] fpc modifiers

2011-04-28 Thread Joerg Schuelke
Am Thu, 28 Apr 2011 23:39:35 +0200 schrieb Hans-Peter Diettrich drdiettri...@aol.com: The bug resides in the dirty Delphi OPL definition. Is it a bug or unspecified behavior? I think it is implemented in the hope it works good enough. If you consume a modifier token as modifier or identifier

[fpc-devel] {$I %LINE%} and friends

2011-04-28 Thread Joerg Schuelke
There is one problem with {$I %LINE%} and his friends, which restricts the use of these directives. They are expanded even inside a macro immediately, so, if you define a macro for debugging purposes, you get the line and file info for the place of the definition and not for the place of the