News for hackers. Stuff that matters.
Re:GCC 6.1 Released by lmm on Wednesday April 27, 2016 @09:54AM (#11580427)
"Valid" in that the standard absolutely requires that compilers give them some particular meaning, no matter how rules-lawyery the compiler is? No. "Valid" in the sense that the intent is perfectly obvious to any reader? Yes, plenty. "bad"? No, unless you use the standard as your definition of good/bad.
Re:GCC 6.1 Released by lomnakkus on Wednesday April 27, 2016 @01:47PM (#11582699)
> the intent is perfectly obvious to any reader

So compilers need to judge what is "perfectly obvious to any reader", now? And you're willing to deal with the fallout of different compilers having different conceptions of "perfectly obvious"?

That's... an ambitious project.

Maybe your time would be better spent convincing the C++ committee to define some more behavior instead of leaving it undefined.

Re:GCC 6.1 Released by lmm on Wednesday April 27, 2016 @05:42PM (#11584814)
The C++ committee exists to standardise the behaviour that major compilers implement. Trying to get them to define behaviour where there isn't already at least broad support would be putting the cart before the horse.