Re: [dws-developer] Inconvenience with TAliasSymbol

[Andreas L. <alu...@we...>]

>>>>>>>>>>>>>>>>>> Urspr=FCngliche Nachricht <<<<<<<<<<<<<<<<<<

Am 11.03.2003, 07:09:09, schrieb Mark <mnm...@co...> zum Thema=20=

[dws-developer] Inconvenience with TAliasSymbol:

> It loses the TColor data type on the array. This is because the TColor=

> type is immediately replaced with the type it represents. This is not =
an
> error, just an inconvenience when using the component editor. There is=

> no way to record the origin of the type.

> Any thoughts on this? Is it a big enough deal to care about? Can
> anything be done about it? Would it be worth it?

I have played a bit with TAliasSymbol (see CVS). With my changes your=20=

problem is no longer a problem. TColor stays TColor.

Because DWS always has to check for =84Aliases=93 there was no need to=20=

replace the alias types by its origin when generating unit symbols.=20

ALu

PS: I introduced a virtual function T[Type]Symbol.BaseType that returns =

the origin type of the requested [type-] symbol. I did this to replace l=
oops=20

while typSym is TAliasSymbol do typSym.Typ;

often found in the base code. Hope that nothing else has been broken ...=