[fpc-devel] Incompatible Types: got "untyped" expected "<procedure variable type of procedure(Pointer);Register>

Micha Nelissen micha at neli.hopto.org
Thu Jul 17 17:49:10 CEST 2008


Craig Peterson wrote:
> Micha Nelissen wrote:
>> Ambiguity depends on whether it takes parameters or not. Return value 
>> would be context sensitive. One doesn't want a context sensitive 
>> language.
> 
> The code presented is perfectly valid in Delphi, so it apparently *is* a 
> context sensitive language, and I'm sure we're not the only developers 
> that appreciate that fact.  The objfpc mode can be as strict as you 

Yes but this has got nothing to do with original poster's problem :-). 
Original poster's problem is about '= nil', not the more general context 
sensitiveness issue.

> want, but it seems like the Delphi mode should work with all of the 
> constructs that Delphi itself allows.  Am I wrong about its intended 
> behavior?

No, AFAICS it's a bug in fpc's delphi mode.

Micha



More information about the fpc-devel mailing list