From: Joe Buck <jbuck@synopsys.com>
To: dhm@paradigm.webvision.com (dave madden)
Cc: mmitchell@usa.net, egcs@cygnus.com
Subject: Re: Static members in templates in egcs-1.0.1
Date: Thu, 15 Jan 1998 16:06:00 -0000 [thread overview]
Message-ID: <199801152058.MAA19999@atrus.synopsys.com> (raw)
In-Reply-To: <199801142030.MAA28506@paradigm.webvision.com>
> I've been trying to find out for a while: does the C++ spec allow you
> to define static consts in the class definition? Egcs & g++ do, but
> all the compilers I've tried on NT complain.
Yes (the standard does allow it), but it is a fairly recent change
(meaning that it isn't widely portable yet).
If you need your code to compile on a variety of C++ compilers I'm
afraid you can't use that feature yet.
next prev parent reply other threads:[~1998-01-15 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-12 20:31 Erik Corry
1998-01-14 0:45 ` Lassi A. Tuura
1998-01-14 4:17 ` Joe Buck
1998-01-14 4:17 ` Erik Corry
1998-01-14 4:17 ` Mark Mitchell
1998-01-14 23:17 ` dave madden
1998-01-15 16:06 ` Mark Mitchell
1998-01-15 16:06 ` Joe Buck [this message]
1998-01-14 23:17 ` Joe Buck
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=199801152058.MAA19999@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=dhm@paradigm.webvision.com \
--cc=egcs@cygnus.com \
--cc=mmitchell@usa.net \
/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).