Michael Van Canneyt wrote:
On Thu, 10 Sep 2009, Florian Klaempfl wrote:
Mattias Gaertner schrieb:
On Thu, 10 Sep 2009 17:52:44 +0200
Florian Klaempfl wrote:
Ivo Steinmann schrieb:
1. Using =nil or Assigned should result in the same.
Afaik not, this was one of the reasons for assigned.
Florian Klaempfl schrieb:
Ivo Steinmann schrieb:
1. Using =nil or Assigned should result in the same.
Afaik not, this was one of the reasons for assigned.
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/
On Thu, 10 Sep 2009, Florian Klaempfl wrote:
Mattias Gaertner schrieb:
On Thu, 10 Sep 2009 17:52:44 +0200
Florian Klaempfl wrote:
Ivo Steinmann schrieb:
1. Using =nil or Assigned should result in the same.
Afaik not, this was one of the reasons for assigned.
Are there any other reasons
Mattias Gaertner schrieb:
> On Thu, 10 Sep 2009 17:52:44 +0200
> Florian Klaempfl wrote:
>
>> Ivo Steinmann schrieb:
>>> 1. Using =nil or Assigned should result in the same.
>> Afaik not, this was one of the reasons for assigned.
>
> Are there any other reasons for assigned?
Distinction between
On Thu, 10 Sep 2009 17:52:44 +0200
Florian Klaempfl wrote:
> Ivo Steinmann schrieb:
> >
> > 1. Using =nil or Assigned should result in the same.
>
> Afaik not, this was one of the reasons for assigned.
Are there any other reasons for assigned?
Mattias
_
Mattias Gärtner wrote:
Zitat von Michael Schnell :
Mattias Gärtner wrote:
Can someone explain why in mode objfpc comparing methods only compares
the address, but not the instance?
Seems perfectly logical to me (@ = Address of, in this case "code
address", the code is the same for all instances
Ivo Steinmann schrieb:
>
> 1. Using =nil or Assigned should result in the same.
Afaik not, this was one of the reasons for assigned.
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
Thank you Peter.
TMethod would have been handy if i knew about this back then. For delphi
compatibility, I had to do this:
program methodpointer;
uses
Classes, sysutils;
type
TMyEvent = procedure of object;
TMyClass = class(TObject)
procedure MyMethod;
end;
{ TMyClass }
procedure
Mattias Gärtner schrieb:
Zitat von Vincent Snijders :
Jonas Maebe schreef:
On 10 Sep 2009, at 14:01, Mattias Gärtner wrote:
Mattias Gärtner wrote:
Can someone explain why in mode objfpc comparing methods only
compares
the address, but not the instance?
Seems perfectly logical to me (@
On Thu, 10 Sep 2009 14:25:26 +, Desmond Coertzen
wrote:
> I have done some horrible code where I needed to know the following:
>
> If TSomeProc = procedure(), then is it easy to determine or set
entry
> vector of ThatProc: TSomeProc by stating ThatProc :=
> @ProcWhereTheCodeLives_InTheCod
In our previous episode, Michael Van Canneyt said:
> > 2) Also the section number is a bit odd. "0.1" - but that's not really a
> > biggy. Maybe the section number could be left out like was done in the
> > ref.xxx document.
> >
> > It's all about consistency. ;-)
>
> I'll have a look at this.
No
I have done some horrible code where I needed to know the following:
If TSomeProc = procedure(), then is it easy to determine or set entry
vector of ThatProc: TSomeProc by stating ThatProc :=
@ProcWhereTheCodeLives_InTheCodeSegment;
It gets more difficult when you work with TSomeClassProc = p
Zitat von Vincent Snijders :
Jonas Maebe schreef:
On 10 Sep 2009, at 14:01, Mattias Gärtner wrote:
Mattias Gärtner wrote:
Can someone explain why in mode objfpc comparing methods only compares
the address, but not the instance?
Seems perfectly logical to me (@ = Address of, in this case
On Thu, 10 Sep 2009, Graeme Geldenhuys wrote:
Hi Michael,
I'm not picking on you, I promise! :-) I'm just doing my bit evaluating
the upcoming FPC 2.4 release - code & docs.
Too late, the intercontinental ballistic missile has left
---[ ref.xxx ]---
1) In the current re
Vincent Snijders het geskryf:
>>
> It is the "compiler switches quick reference chart". Or maybe better
> ""compiler switches quick reference card".
Ah, like the ones in the "Dummies guide of ..." books. :-) Then maybe
"quickref.xxx" is a better name than "chart.xxx" - that's if we limit
ourselve
Hi Michael,
I'm not picking on you, I promise! :-) I'm just doing my bit evaluating
the upcoming FPC 2.4 release - code & docs.
---[ ref.xxx ]---
1) In the current ref.ps & ref.pdf documents, page 6 doesn't contain a
header, where all pages before and after it has got headers (which
Zitat von Jonas Maebe :
On 10 Sep 2009, at 14:01, Mattias Gärtner wrote:
Mattias Gärtner wrote:
Can someone explain why in mode objfpc comparing methods only compares
the address, but not the instance?
Seems perfectly logical to me (@ = Address of, in this case "code
address", the code is
Zitat von Thaddy :
Mattias Gärtner wrote:
Zitat von Michael Schnell :
Mattias Gärtner wrote:
Can someone explain why in mode objfpc comparing methods only compares
the address, but not the instance?
Seems perfectly logical to me (@ = Address of, in this case "code
address", the code is the
Graeme Geldenhuys schreef:
Michael Van Canneyt het geskryf:
If you have a suggestion, I'll be glad to change the name.
So the name and content is correct? Umm, so how did you get to the name
"chart"? :-) When I opened that file, I expected the class hierarchy
chart - you know, like the one Bor
Michael Van Canneyt het geskryf:
>
> If you have a suggestion, I'll be glad to change the name.
So the name and content is correct? Umm, so how did you get to the name
"chart"? :-) When I opened that file, I expected the class hierarchy
chart - you know, like the one Borland gave with D7 & K3.
U
On Thu, 10 Sep 2009, Graeme Geldenhuys wrote:
Hi,
I downloaded a while back the FPC 2.2.0 and 2.2.4 documentation in PDF
and PS format. In both cases the chart.* files were incorrect (I believe).
The filename implies a "chart", so I gathered that it is a class chart /
hierarchy of some kind.
Hi,
I downloaded a while back the FPC 2.2.0 and 2.2.4 documentation in PDF
and PS format. In both cases the chart.* files were incorrect (I believe).
The filename implies a "chart", so I gathered that it is a class chart /
hierarchy of some kind. But when I view it, it is just a listing of the
lo
Jonas Maebe schreef:
On 10 Sep 2009, at 14:01, Mattias Gärtner wrote:
Mattias Gärtner wrote:
Can someone explain why in mode objfpc comparing methods only compares
the address, but not the instance?
Seems perfectly logical to me (@ = Address of, in this case "code
address", the code is the
Mattias Gärtner wrote:
Zitat von Michael Schnell :
Mattias Gärtner wrote:
Can someone explain why in mode objfpc comparing methods only compares
the address, but not the instance?
Seems perfectly logical to me (@ = Address of, in this case "code
address", the code is the same for all instanc
On 10 Sep 2009, at 14:01, Mattias Gärtner wrote:
Mattias Gärtner wrote:
Can someone explain why in mode objfpc comparing methods only
compares
the address, but not the instance?
Seems perfectly logical to me (@ = Address of, in this case "code
address", the code is the same for all instan
Zitat von Michael Schnell :
Mattias Gärtner wrote:
Can someone explain why in mode objfpc comparing methods only compares
the address, but not the instance?
Seems perfectly logical to me (@ = Address of, in this case "code
address", the code is the same for all instances of a class).
OnClic
Mattias Gärtner wrote:
Hi,
Can someone explain why in mode objfpc comparing methods only compares
the address, but not the instance?
For example:
a:=TMyClass.Create;
b:=TMyClass.Create;
if @a.test = @b.test then writeln('the same method');
This results in strange behaviors, when using
Mattias Gärtner wrote:
> Can someone explain why in mode objfpc comparing methods only compares
> the address, but not the instance?
Seems perfectly logical to me (@ = Address of, in this case "code
address", the code is the same for all instances of a class).
-Michael
___
Hi,
Can someone explain why in mode objfpc comparing methods only compares
the address, but not the instance?
For example:
a:=TMyClass.Create;
b:=TMyClass.Create;
if @a.test = @b.test then writeln('the same method');
This results in strange behaviors, when using the following code (fro
Fixed, thanks for reporting.
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
30 matches
Mail list logo
