public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Phil Edwards <pedwards@disaster.jaj.com>
To: Gabriel Dos Reis <gdr@codesourcery.com>
Cc: dewar@gnat.com, fw@deneb.enyo.de, bosch@gnat.com,
	dnovillo@redhat.com, gcc@gcc.gnu.org, kenner@vlsi1.ultra.nyu.edu,
	zack@codesourcery.com
Subject: Really crummy error messages, was Re: Ada files now checked in
Date: Sun, 07 Oct 2001 14:34:00 -0000	[thread overview]
Message-ID: <20011007173547.A15654@disaster.jaj.com> (raw)

On Sun, Oct 07, 2001 at 04:19:16PM +0200, Gabriel Dos Reis wrote:
> dewar@gnat.com writes:
> 
> | j.adb:3:04: "xyz" is undefined
> | 
> | compared to the c message
> | 
> | j.c:1: `asdf' undeclared (first use this function)
> 
> For a non-native English speaker like me, I have always questioned
> myself why the latter choice (which I find odd and difficult to read)
> is current practice and not the former.  FWIW, I would suggest that we
> switch to Robert's suggestion.

Even native English speakers, like me, get confused, and here's why:

For "first use this function" to be a correct English sentence [fragment],
there is only one possible parse, and it's not what is intended.  "First use
this function" is an /imperative/ with "use" as a verb (pronounced with a 'z'
sound), and always leaves new users wondering, "first use /which/ function?"

But GCC wants "use" to be a noun, pronounced with an 's' sound.  What we
really want to say is any of:

    j.c:1: `asdf' undeclared (first use in this function)
    j.c:1: `asdf' undeclared (first time used in this function)
    j.c:1: `asdf' undeclared (first occurrence in this function)

(Although maybe "is undeclared" would be better for C than "is undefined.")

Please, let's fix this.


Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams

             reply	other threads:[~2001-10-07 14:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-07 14:34 Phil Edwards [this message]
2001-10-07 23:01 ` Really crummy error messages Florian Weimer
2001-10-08 11:09 ` Really crummy error messages, was Re: Ada files now checked in Zack Weinberg
2001-10-08 13:31   ` Phil Edwards
2001-10-08 16:49     ` Tim Hollebeek
2001-10-09 23:32       ` Fergus Henderson
2001-10-10  2:25         ` Florian Weimer
2001-10-10 11:00         ` Phil Edwards
2001-10-11 14:04     ` Zack Weinberg

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=20011007173547.A15654@disaster.jaj.com \
    --to=pedwards@disaster.jaj.com \
    --cc=bosch@gnat.com \
    --cc=dewar@gnat.com \
    --cc=dnovillo@redhat.com \
    --cc=fw@deneb.enyo.de \
    --cc=gcc@gcc.gnu.org \
    --cc=gdr@codesourcery.com \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    --cc=zack@codesourcery.com \
    /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).