From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: can we avoid using contractions in GDB messages?
Date: Mon, 07 Mar 2011 11:30:00 -0000 [thread overview]
Message-ID: <E1PwYXs-0000IB-Dl@fencepost.gnu.org> (raw)
In-Reply-To: <20110307105158.GZ30306@adacore.com> (message from Joel Brobecker on Mon, 7 Mar 2011 14:51:58 +0400)
> Date: Mon, 7 Mar 2011 14:51:58 +0400
> From: Joel Brobecker <brobecker@adacore.com>
>
> > + if (minsym == NULL)
> > + error (_("Error reading inferior's overlay table: couldn't "
> > + "find `_ovly_table' array\n"
> > + "in inferior. Use `overlay manual' mode."));
>
> I'm not very fond of contractions in error messages (or any message
> printed by GDB). I know there is plenty of "prior art" of our use
> of contractions in the output, but I just think it looks better to
> spell words completely. For the future, can we agree on avoiding
> contractions?
You mean, use "could not" instead of "couldn't"? Why is that an
issue?
next prev parent reply other threads:[~2011-03-07 11:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 0:56 [commit] symfile.c (simple_overlay_update): Check for null return Michael Snyder
2011-03-07 11:07 ` can we avoid using contractions in GDB messages? (was: "[commit] symfile.c (simple_overlay_update): Check for null return.") Joel Brobecker
2011-03-07 11:30 ` Eli Zaretskii [this message]
2011-03-07 12:14 ` can we avoid using contractions in GDB messages? Joel Brobecker
2011-03-07 19:07 ` Michael Snyder
2011-03-07 19:19 ` Paul Koning
2011-03-08 4:54 ` Joel Brobecker
2011-03-07 21:58 ` can we avoid using contractions in GDB messages? (was: "[commit] symfile.c (simple_overlay_update): Check for null return.") Mike Frysinger
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=E1PwYXs-0000IB-Dl@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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