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
token or an token relies on context information. But what is
that context? An example:
type
name=procedure;
cdecl=integer;
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 infor
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
> token or an token relies on c
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)
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 - fpc-devel@lists.freep
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 token he needs a lookup of
only
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 a
Am Thu, 28 Apr 2011 20:09:59 +0200
schrieb Joerg Schuelke :
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 - fpc-devel@lists.fre
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 - fpc-devel@lists.freepascal.
Am Thu, 28 Apr 2011 23:39:35 +0200
schrieb Hans-Peter Diettrich :
> 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 token as or in
respect of the right context of one token,
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 expans
11 matches
Mail list logo
