From: Joe Buck <jbuck@synopsys.com>
To: kaz@cafe.net (Kaz Kylheku)
Cc: Gabriel.Dos-Reis@dptmaths.ens-cachan.fr, Joe@synopsys.com,
Buck@synopsys.com, jbuck@synopsys.com, g++@cygnus.com,
egcs@cygnus.com
Subject: RE: implicit declaration in C++ considered harmful
Date: Wed, 08 Apr 1998 17:25:00 -0000 [thread overview]
Message-ID: <199804082207.PAA24305@atrus.synopsys.com> (raw)
In-Reply-To: <01BD62F9.19A03370.kaz@cafe.net>
> > I think EGCS should be standard conforming and flags implicit
> > declaration as an error not a warning.
>
> The C and C++ standards don't distinguish errors and warnings,
> though I say this with somewhat less than full confidence because
> I'm not as familiar with the C++ draft as with the C standard.
Yes, we technically comply, but nevertheless the current behavior
is not desirable.
next prev parent reply other threads:[~1998-04-08 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-08 21:20 Kaz Kylheku
1998-04-08 17:25 ` Joe Buck [this message]
1998-04-09 18:29 ` Martin von Loewis
-- strict thread matches above, loose matches on Subject: below --
1998-04-08 2:13 Joe Buck
1998-04-08 7:35 ` Gabriel Dos Reis
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=199804082207.PAA24305@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=Buck@synopsys.com \
--cc=Gabriel.Dos-Reis@dptmaths.ens-cachan.fr \
--cc=Joe@synopsys.com \
--cc=egcs@cygnus.com \
--cc=g++@cygnus.com \
--cc=kaz@cafe.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).