__STDCPP__ anybody?

Doug Gwyn gwyn at brl-smoke.ARPA
Wed Jun 29 03:04:57 AEST 1988


In article <2460 at plus5.UUCP> hokey at plus5.UUCP (Hokey) writes:
>It appears you are advocating two items.
>First, no new/additional features should be added because they are
>nonstandard (or perhaps "inventive" (Hi, ado!)).

No, you asked whether __STDCPP__ would be useful.  To be useful for the
intended purpose, you would have to have it defined for all Standard-
conforming preprocessors.  Since it is not in the Standard, it won't be
so defined.  Therefore it is not useful.

>Second, since it is possible to write code which will interpret on both old
>and Standard preprocessors, we should do so.  Therefore, why bother with
>all these new mechanisms anyway?

Certainly if you are concerned with both compilation environments, it
is generally more work to provide code for each separately than to just
use their common intersection.



More information about the Comp.lang.c mailing list