[fpc-devel] {$calling register} compiler-directive at wrong place (bug 12881)

Jonas Maebe jonas.maebe at elis.ugent.be
Sun Jan 11 22:52:33 CET 2009

On 11 Jan 2009, at 18:40, Joost van der Sluis wrote:

> Now the problem seems to be that the function defined directly before
> the {$calling register} directive is already defined as register.

Many bugs like that have been fixed in the scanner in the past. There  
are workarounds to prevent this sort of stuff from happening for all  
the checks directives ({$r+/-}, {$i+/-}, {$q+/-}, ...), for {$push}/ 
{$pop}, etc... Basically such changes have to be cached when processed  
and flushed later.

Please file a bug report.


More information about the fpc-devel mailing list