[cfe-dev] Source information for types

[Argyrios Kyrtzidis]

On Aug 8, 2009, at 2:38 AM, Enea Zaffanella wrote:

>>> Another issue that could be solved by following this proposal is  
>>> the ability to distinguish different syntactic representations of  
>>> the same type; namely, distinguishing "unsigned" from "unsigned  
>>> int" from "int unsigned" and the like.
>> What are the use cases for this, do you also need it to check  
>> adherence to coding standards ?
>
> Yes. (In this particular case, I suspect that coding standard  
> checkers are the only application.)


Is re-lexing the type specifier a reasonable solution for this ?
My concern is the impact on memory consumption for type source info.  
Ideally memory usage for type source info should be reasonable enough  
to consider having them on all the time.

-Argiris