Is there a preferred place to submit compiler bug reports? The bug tracking page on the…
you wrote 5 lines
You can always report them under 1.0.6, most times the bug is also present in that release
Peter

Mailing lists / lazarus / 2003-06
5 messages · 3 people ·
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
Is there a preferred place to submit compiler bug reports? The bug tracking page on the…
You can always report them under 1.0.6, most times the bug is also present in that release
Peter
Is there a preferred place to submit compiler bug reports? The bug tracking page on the FPC site doesn't seem to include 1.0.7.
I've developed workarounds for the problems I've found... but I thought it might be useful to post them somewhere.
-Tom
You can always report them under 1.0.6, most times the bug is also present in that release
You can always report them under 1.0.6, most times the bug is also present in that release
Thanks. On second thought, I'm not sure if the problem I'm seeing is a bug or a compiler implementation issue. The Delphi compiler resolves call references to a declared function type and variable such as:
Type
TickCallFunc = function:Int64;
SomeClass = Class
FTicks:TickCallFunc;
end;
;
Procedure LocalProc;
Var LocalVar:Int64;
Begin
LocalVar:=FTicks;In FPC, the compiler quits at the assignment with a type incompatibility between TickCallFunc and int64. Does FPC support this syntax?
-Tom
You can always report them under 1.0.6, most times the bug is also present in that release
Procedure LocalProc; Var LocalVar:Int64; Begin LocalVar:=FTicks;
Sorry... just figured it out: LocalVar:=FTicks(); works!You can always report them under 1.0.6, most times the bug is also present in that release
Yes, in Delphi mode it allows such ambigious statements. In objfpc mode you have to write unambigious. That means, you dont want the variable FTicks, you want to call the function. So, you have to write
LocalVar:=FTicks();Mattias