On 07/01/19 20:12, Mattias Gaertner via fpc-devel wrote:
On Mon, 7 Jan 2019 19:24:53 +0100
Jonas Maebe wrote:
Object class methods do have a self parameter. If an object has a
vmt, the object class methods get this vmt pointer passed as self
parameter. Otherwise they get nil as self
On Mon, 7 Jan 2019 19:24:53 +0100
Jonas Maebe wrote:
> On 07/01/19 17:32, Mattias Gaertner via fpc-devel wrote:
> > True, reason is that *non* static means there is a Self.
> > But since there is no "object of objecttype" and no "record of
> > recordtype", there is no type for Self in class
On 07/01/19 17:32, Mattias Gaertner via fpc-devel wrote:
True, reason is that *non* static means there is a Self.
But since there is no "object of objecttype" and no "record of
recordtype", there is no type for Self in class methods of
objects/record.
Object class methods do have a self
Am 07.01.2019 um 17:13 schrieb Sven Barth via fpc-devel:
Did you try to add "static" to the TDiaPosition.Equals class function?
For an object type only instance and static class methods make sense
so non static class methods should probably best be forbidden.
That did the trick. Thank you.
On Mon, 7 Jan 2019 17:13:21 +0100
Sven Barth via fpc-devel wrote:
>[...]
> Did you try to add "static" to the TDiaPosition.Equals class
> function? For an object type only instance and static class methods
> make sense so non static class methods should probably best be
> forbidden.
True,
Am Mo., 7. Jan. 2019, 15:55 hat Werner Pamler
geschrieben:
> FPC trunk has not been very friendly to existing code recently...
>
> Today with r40792, the TAChart package fails to recompile:
> "tadiagram.pas(347,38) Error: Only static methods and static variables
> can be referenced through an
FPC trunk has not been very friendly to existing code recently...
Today with r40792, the TAChart package fails to recompile:
"tadiagram.pas(347,38) Error: Only static methods and static variables
can be referenced through an object type". The faulty code is
operator = (const A, B:
