Re: [fpc-devel] Propose: change TComponent.Tag from longint to PtrInt

2006-09-04 Thread Mattias Gaertner
On Mon, 4 Sep 2006 07:13:53 +0200 Martin Schreiber [EMAIL PROTECTED] wrote: On Monday 04 September 2006 02.55, Luiz Americo wrote: I'd like to propose change TComponent.Tag type from longint to PtrInt. I know it's not a good programing practice, but sometimes this property can be used to

Re: [fpc-devel] Propose: change TComponent.Tag from longint to PtrInt

2006-09-04 Thread Daniël Mantione
Op Mon, 4 Sep 2006, schreef Mattias Gaertner: Me2. Just one disadvantage: The Tag is published. If someone stores a 64bit value and the component is stored, the stream can not be read under 32bit anymore. ...which makes it impossible to use streams for anything derived from Tcomponent,

Re: [fpc-devel] Propose: change TComponent.Tag from longint to PtrInt

2006-09-04 Thread Vincent Snijders
Daniël Mantione schreef: Op Mon, 4 Sep 2006, schreef Mattias Gaertner: Me2. Just one disadvantage: The Tag is published. If someone stores a 64bit value and the component is stored, the stream can not be read under 32bit anymore. ...which makes it impossible to use streams for anything

[fpc-devel] makeskel fails to parse file

2006-09-04 Thread Graeme Geldenhuys
Hi, I am using the latest FPC 2.0.5 from SubVersion. (rev 4550). I am trying to promote fpdoc to the tiOPF developers and hit a brick wall with my first attempt! :-( I am trying to run makeskel against a project I work on (tiOPF), but makeskel keeps giving me the error below. I created a

Re: [fpc-devel] Propose: change TComponent.Tag from longint to PtrInt

2006-09-04 Thread Mattias Gaertner
On Mon, 04 Sep 2006 11:56:06 +0200 Vincent Snijders [EMAIL PROTECTED] wrote: Daniël Mantione schreef: Op Mon, 4 Sep 2006, schreef Mattias Gaertner: Me2. Just one disadvantage: The Tag is published. If someone stores a 64bit value and the component is stored, the stream can

Re: [fpc-devel] Propose: change TComponent.Tag from longint to PtrInt

2006-09-04 Thread Vincent Snijders
Daniël Mantione schreef: Op Mon, 4 Sep 2006, schreef Vincent Snijders: Daniël Mantione schreef: Op Mon, 4 Sep 2006, schreef Mattias Gaertner: Me2. Just one disadvantage: The Tag is published. If someone stores a 64bit value and the component is stored, the stream can not be read under

Re: [fpc-devel] Propose: change TComponent.Tag from longint to PtrInt

2006-09-04 Thread Marc Weustink
Marc Weustink wrote: Michael Van Canneyt wrote: On Mon, 4 Sep 2006, peter green wrote: Me2. Just one disadvantage: The Tag is published. If someone stores a 64bit value and the component is stored, the stream can not be read under 32bit anymore. ...which makes it impossible to use

Re: [fpc-devel] Propose: change TComponent.Tag from longint to PtrInt

2006-09-04 Thread Mattias Gaertner
On Mon, 04 Sep 2006 13:16:11 +0200 Vincent Snijders [EMAIL PROTECTED] wrote: Daniël Mantione schreef: Op Mon, 4 Sep 2006, schreef Vincent Snijders: Daniël Mantione schreef: Op Mon, 4 Sep 2006, schreef Mattias Gaertner: Me2. Just one disadvantage: The Tag is published. If

RE: [fpc-devel] Propose: change TComponent.Tag from longint to PtrInt

2006-09-04 Thread peter green
...which makes it impossible to use streams for anything derived from Tcomponent, which is really a lot. I don't think we should break this feature to allow broken code to work. BTW even borland themselves seemed to promote its use for storing pointers from delphi 3 help: Tag has no

Re: [fpc-devel] Propose: change TComponent.Tag from longint to PtrInt

2006-09-04 Thread Luiz Americo Pereira Camara
Daniël Mantione wrote: In 16 bit days it was considered acceptable to typecast pointers into records and just increase their offset. However, it was not portable. Making your code portable requires some effort. This kind of code is just one example of things you should not do in portable code.