> ...thus the need, while the compiler bug is being investigated, to
> determine whether the code is non-standard. Of course, common things
> are well-tested; it is things on the edge of the standard---possibly
> requiring interpretations---which can cause trouble. Again, one can and
> should separate the two questions: compiler bug? standard code?
As Malcolm pointed out, the compiler vendor can also provide other
information than whether or not there is a problem with the compiler.
But such things "on the edge of the standard" are often of interest to
other users and it is a good idea to "exercise" one's own compiler with
such code.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|