This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: TR library extensions


Martin Sebor <sebor@roguewave.com> writes:

| So I agree with Petur: a quality implementation of C++ such as gcc
| should provide an option for programs to choose the version of the
| C++ standard they want to conform to, and the compiler should
| diagnose detectable violations when the option is selected.

By that definition of "strict conformance" you're also arguing for
rejecting a program that includes <unistd.h>.

As far as the standard goes, whether <unistd.h> is accepted is
at best implementation defined.  By that same token, accepting <types>
is implementation defined.  If your documentation tells you that
configuring the compiler with TR support will include TR semantics,
that is it.  Just like we do for C99 stuff.  We don't reject programs
that happen to include <tgmath.h> just on the mere assumption that
-std=c++98 is specified.

-- Gaby


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]