2012/4/30 Michael Goffioul <michael.goffi...@gmail.com>: > Until gcc-4.7, missing return statements was a MSVC-only problem.
As Mike pointed out, this has been UB since C++98, so it's certanly not an MSVC-only problem. We don't generally cater to compiler bugs, even though sometimes, rarely, we do for gcc. We are conservative about implementation-defined features (e.g. #pragma) and about missing features (C++11 is mostly off-limits for at least a couple more years), but that's it. By the way, it appears that this particular UB is compiled by g++ 4.7, and all g++'s I've ever used have already emitted an optional diagnostic for it. So it's not like it's getting fixed now only becaue a newer version of g++ got more strict about how it decided to handle this situation. So, if there are problems with the code, even if it's problems that MSVC found but clang or gcc or icc didn't find, and they really are problems and not compiler bugs, then please do patch the relevant Octave or Octave-Forge code. - Jordi G. H. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
