Re: OT Verifying code across gcc versions [Re: Commercial support on GCC/G++ open source versions]

[Paul Pluzhnikov]

Paul Pluzhnikov <ppluzhnikov-nsp@charter.net> writes:

> How does the fact that your code is strictly standard help you
> verify that none of it is mis-compiled or mis-optimized?

I realized that (probably much more common then optimizer bugs) 
cause of breakage when moving to a newer version of the compiler is
"buggy code that just happens to work when compiled with the older
compiler".
Such buggy code may still be perfectly standard ANSI C++.

But my question still stands:

> So what gives you confidence to "jump to new version as soon as it
> is released"?

Thanks.
-- 
In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email.