You still have not demonstrated that this is a real problem. If someone is having a real problem, then we can offer them a simple sed script to fix it.
If I am recalling the original posting correctly, the fact that gcc behaves differently to "most other compilers" is the actual problem. Issues relating to code correctness, user brain-deadednes, or even just sensible practices are rather moot. gcc can be the only Johnny in step, or it can behave, as Mr. Hinnant was suggesting, the way everyone else does and adopt the de-facto standard.
Writing sed scripts that change source code is likely to be very unpalletable to some users. If you're working in an ISO9000 environment where every single source line change is tracked by a rather burdensome process, the last thing you want to do is invoke that process for some source base simply because the new compiler you are moving to behaves differently to the last 5 compilers you used. Just my $0.02. Kean
