[Issue 249] New: circular typedef and alias bugs

[Sean Kelly]

Walter Bright wrote:
> Derek Parnell wrote:
>> On Tue, 11 Jul 2006 15:53:11 +1000, Walter Bright 
>> <newshound at digitalmars.com> wrote:
>>
>>> James Pelcis wrote:
>>>> I think that the error messages are good, even if they aren't 
>>>> perfect. My point is that those four pieces of code are essentially 
>>>> the same but all four produce different error messages.  Could they 
>>>> all be made the same?
>>>
>>> I like to keep error messages generated by different parts of the 
>>> compiler slightly different - makes it easier to track them down.
>>
>> Try using message IDs like most professional designers do. They are 
>> LOTS more easier to track, document and maintain.
> 
> LOL. I use message IDs in the C++ compiler. I like using the text ones 
> better. (And the issue is the same, if message X comes up, I like it 
> generated in one place, which means each message ID must be used only 
> once.)

Perhaps a context ID would be useful?  Could even encode it into the 
message ID--set the upper N bits as the message pointer and the lower N 
bits as the location.  Still not quite as easy to track down as a search 
for an embedded string though, I'll admit.


Sean