From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Martin von Loewis <martin@mira.isdn.cs.tu-berlin.de>
Cc: egcs@cygnus.com
Subject: Re: G++ Bug List
Date: Sun, 25 Oct 1998 04:08:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.05.9810251230290.14779-100000@nashira.dbai.tuwien.ac.at> (raw)
In-Reply-To: <199810231101.MAA00699@mira.isdn.cs.tu-berlin.de>
On Fri, 23 Oct 1998, Martin von Loewis wrote:
> I started a list of bugs that are frequently reported, yet unlikely to
> get fixed anytime soon. I'd like to see this document in
> htdocs/c++bugs.html, and referenced from the FAQ.
Me, too. :-) Consider it approved, modulo the remarks below.
Please also add a link at the end of the "How to report bugs" FAQ Entry.
Perhaps we might want to rename that to "How to report bugs / Frequently
reported bugs".
> <title>EGCS g++ Frequently Detected Bugs</title>
I suggest to use "C++" or "C++ frontend" instead of "g++" to avoid
confusion. AFAIS, g++ is not that well-known a ``concept'' and many
users are actually invoking it as `gcc` or `c++`.
> <h1>G++ FDB List</h1>
Please refrain from introducing additional three-letter words. ;-)
Finally, I recommend to always add _explicit_ notes about the latest
release and its behavior. How about replacing "egcs-2.92.15" by "egcs 1.1
and egcs-2.92..." in various places?
Thanks for that effort!
Gerald
--
Gerald Pfeifer (Jerry) Vienna University of Technology
pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
next prev parent reply other threads:[~1998-10-25 4:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-23 4:36 Martin von Loewis
1998-10-25 4:08 ` Gerald Pfeifer [this message]
[not found] <199810231101.MAA00699.cygnus.egcs@mira.isdn.cs.tu-berlin.de>
1998-10-24 3:17 ` Jason Merrill
1998-10-24 5:16 Ryszard Kabatek
1998-10-25 13:53 ` Martin von Loewis
[not found] <Pine.LNX.3.96.981024133916.3594A-100000.cygnus.egcs@rumcajs.chemie.uni-halle.de>
1998-10-24 18:22 ` Jason Merrill
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=Pine.GSO.4.05.9810251230290.14779-100000@nashira.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=egcs@cygnus.com \
--cc=martin@mira.isdn.cs.tu-berlin.de \
/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).