From: Laurent Guerby <guerby@acm.org>
To: fjh@cs.mu.oz.au
Cc: dewar@gnat.com, Anshil@gmx.net, aoliva@redhat.com, gcc@gcc.gnu.org
Subject: Re: Warning Messages (was: Is this a gcc bug?)
Date: Sat, 13 Jan 2001 11:13:00 -0000 [thread overview]
Message-ID: <200101131914.UAA01872@ulmo> (raw)
In-Reply-To: <20010113142913.A30791@hg.cs.mu.oz.au>
An alternative solution for warnings where the only valid hint is one
paragraph long (or more ;-), is to put a really short one, even if
mysterious, plus "see GCC documentation for more information" or "GCC
documentation has more information", and have sections "Common
Warnings for Language X" in the compiler manual detailing the
issues. Such a solution would solve cleanly the education issue, and
the "meta-education" issue: there's a manual dude! ;-).
I often found that people ask themselves questions the first time they
see a warning, then the messages is just an id and it's better when
it's short in listings.
--
Laurent Guerby <guerby@acm.org>
prev parent reply other threads:[~2001-01-13 11:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-12 19:15 Is this a gcc bug? dewar
2001-01-12 19:29 ` Fergus Henderson
2001-01-13 11:13 ` Laurent Guerby [this message]
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=200101131914.UAA01872@ulmo \
--to=guerby@acm.org \
--cc=Anshil@gmx.net \
--cc=aoliva@redhat.com \
--cc=dewar@gnat.com \
--cc=fjh@cs.mu.oz.au \
--cc=gcc@gcc.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).