From: Mike Stump <mrs@windriver.com>
To: gcc@gcc.gnu.org, nbecker@fred.net
Subject: Re: Why is this code accepted?
Date: Mon, 16 Apr 2001 14:58:00 -0000 [thread overview]
Message-ID: <200104162158.OAA20152@kankakee.wrs.com> (raw)
> To: gcc@gcc.gnu.org
> From: nbecker@fred.net
> Date: 16 Apr 2001 16:27:42 -0400
> This code compiles without complaint both on gcc-2.96 and on a
> recent gcc-3 snapshot, but doesn't link. I suspect the
> initialization of the static "a" is invalid (I don't have a good
> reference handy), but isn't gcc behaviour wrong?
There was a g++ feature that allowed this to work, a while ago.
Someone broke that feature, and didn't remove the feature from all
places in the compiler that supported the feature. As I recall, the
standard doesn't support this feature.
next reply other threads:[~2001-04-16 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-16 14:58 Mike Stump [this message]
2001-04-16 20:16 ` Alexandre Oliva
2001-04-17 4:57 ` nbecker
2001-04-17 14:52 ` Alexandre Oliva
-- strict thread matches above, loose matches on Subject: below --
2001-04-17 19:41 Mike Stump
2001-04-17 17:20 Mike Stump
2001-04-16 13:27 nbecker
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=200104162158.OAA20152@kankakee.wrs.com \
--to=mrs@windriver.com \
--cc=gcc@gcc.gnu.org \
--cc=nbecker@fred.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).