Re: [Opencxx-users] understanding TypeInfo

[Stefan S. <se...@sy...>]

Grzegorz Jakacki wrote:

> Hm... Maybe we really should not bother with this laziness for now... 
> However we may have problems later, since e.g. in refactoring when using 
> some existing type to produce new declarations it is very desirable to 
> have it in least expanded form. Could you briefly show what exactly
> would be substantially easier?

well, right now it is for me still a matter of understanding, not implementing.
Your hint at intelligible error messages using the un-normalized name is
very valuable. It suggests that normalizing is not just an internal detail
of optimizing, but rather that it may be useful to make this more explicit,
i.e. make it possible for the user to access a typeinfo both in its expanded
and non-expanded form.

Hmm, but to understand the matter better I have to see encodings and typeinfos
in use. This may even be a good candidate for some unit tests:

* parse some declarations
* inspect (dump) the generated encodings
* regenerate new ptrees from these encodings
* compare these with the original declarations

That would be a very good demonstration / documentation as well as a good
test case.

Regards,
		Stefan