From: jstack@cylink.com (Joe Stack)
To: <gnu@gnu.org>
Subject: GNUC C Compiler Extensions
Date: Tue, 25 Jan 2000 10:48:00 -0000 [thread overview]
Message-ID: <200001251848.NAA29213@delysid.gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 762 bytes --]
Hi,
I'm trying to figure out how to enable (the otherwise default) C++ Comments
feature described in the documentation.
In test code I've determined that the __GNUC__ preproc constant is defined
and __STRICT_ANSI__ and __STDC__ are NOT defined (as per the documentation).
I've visited various versions of the compiler documentation and all I've
found it that it is supposed enabled by default and disabled by '-ansi' or
'-traditional'.
The version of the compiler we're running is given as 2.5.6 (solaris2).
Which leaves the question... How does one enable the acceptance of these
extended features (particularly, for the moment, the C++ Comments) and at
which version were they added?
I appreciate your help figuring this out!
Tx,
Joe Stack
Cylink/3SC
[-- Attachment #2: winmail.dat --]
[-- Type: application/vnd.ms-tnef, Size: 1940 bytes --]
WARNING: multiple messages have this Message-ID
From: jstack@cylink.com (Joe Stack)
To: <gnu@gnu.org>
Subject: GNUC C Compiler Extensions
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <200001251848.NAA29213@delysid.gnu.org> (raw)
Message-ID: <20000401000000.r64aYErw45RXTFOsSHW2IuRV1kA7JB41ZQa31xPsga4@z> (raw)
[-- Attachment #1: Type: text/plain, Size: 762 bytes --]
Hi,
I'm trying to figure out how to enable (the otherwise default) C++ Comments
feature described in the documentation.
In test code I've determined that the __GNUC__ preproc constant is defined
and __STRICT_ANSI__ and __STDC__ are NOT defined (as per the documentation).
I've visited various versions of the compiler documentation and all I've
found it that it is supposed enabled by default and disabled by '-ansi' or
'-traditional'.
The version of the compiler we're running is given as 2.5.6 (solaris2).
Which leaves the question... How does one enable the acceptance of these
extended features (particularly, for the moment, the C++ Comments) and at
which version were they added?
I appreciate your help figuring this out!
Tx,
Joe Stack
Cylink/3SC
[-- Attachment #2: winmail.dat --]
[-- Type: application/vnd.ms-tnef, Size: 1940 bytes --]
next reply other threads:[~2000-01-25 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-25 10:48 Joe Stack [this message]
2000-04-01 0:00 ` Joe Stack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200001251848.NAA29213@delysid.gnu.org \
--to=jstack@cylink.com \
--cc=gnu@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).