[fpc-devel]TReader.ReadPropValue

[Mattias Gaertner]

On Sat, 06 Dec 2003 00:25:25 +0100  Florian Klaempfl
<Florian.Klaempfl at gmx.de> wrote:

> Mattias Gaertner wrote:
> > unique pointer for each type. But fpc 1.0.x and 1.9.x returns different
> > values, depending on where you use the TypeInfo function. In this case:
> > TypeInfo(TColor) called in graphics.pp returns a different value than
> > called in classes.pp.
> 
> Submit a bug report and we'll fix it soon or later :)

Done.

 
> > One solution would be to add a further list of IntToIdent functions
> > identified by names instead of TypeInfo. The disadvantage is, that it
> > can be ambgious. But since the TypeInfo registering does not work, it is
> > not used, so this workaround will not break any code. And what is more
> > important: These things are rarely used, so as soon as the TypeInfo
> > works, we only need to change a few lines of code.
> > 
> > 
> > About the addition: I think, it can be useful for alias enums (e.g.
> > myenum =(a:=b, c:=d, ...) ). What do the fpc devels think about?
> 
> The enums are still not compatible.

Ok. You need to map alias names to enum names instead and then use
GetEnumName. OTOH this is just a goodie.

What about the alternative workaround for the integers? This is needed for
streaming Delphi forms.


Mattias