Re: New C parser [patch]

[Zack Weinberg <zack@codesourcery.com>]

"Joseph S. Myers" <jsm@polyomino.org.uk> writes:

> The regressions in English messages in the C++ front end are separate from 
> the i18n problems.  For now, my parser uses literal '' to get properly 
> formatted English messages.  When this area is cleaned up, or if 
> c_parse_error starts accepting %<%>, then it can start using %<%>.  For 
> now, the i18n is no worse than with the existing parser, and a key design 
> feature of this patch is that it tries to be as minimal as possible for a 
> parser replacement: it will follow cleanups made to the existing code 
> before it goes in, and it will facilitate further cleanups once it is in, 
> but will avoid leading on cleanups or changes that don't need entangling 
> with a new parser.  I will however put ??? comments anywhere (as here) 
> where it is suggested that the status quo is a mess and a good subject for 
> a future cleanup.

That's fine.  Just to be clear, I wrote down everything that came to
mind, without trying to distinguish between things that needed fixing
right now and things that should get fixed eventually.  I'm in
agreement with the plan of not entangling other changes with the
parser replacement.

zw