From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: can we avoid using contractions in GDB messages? (was: "[commit] symfile.c (simple_overlay_update): Check for null return.")
Date: Mon, 07 Mar 2011 21:58:00 -0000 [thread overview]
Message-ID: <201103071552.00959.vapier@gentoo.org> (raw)
In-Reply-To: <20110307105158.GZ30306@adacore.com>
[-- Attachment #1: Type: Text/Plain, Size: 1399 bytes --]
On Monday, March 07, 2011 05:51:58 Joel Brobecker wrote:
> Just a suggestion. It's really a detail, and I won't push for us
>
> to adopt this suggestion, but:
> > + 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.
personally, i think contractions are fine when used correctly. while i am a
lazy english speaker, "should not" makes it sound like a formal statement. i
also just watched a hindi movie where the subtitles were kind of bad, but for
the opposite reason ... they used contractions everywhere even when native
speakers wouldn't (because it sounds weird).
what about "cannot" vs "can not" ? obviously "can't" is out via this new
rule, but i don't see a problem with "cannot" ...
i think some people read "maybe" as a contraction of "may be", but i see a
subtle difference between them.
> For the future, can we agree on avoiding contractions?
in order to make it stick, it really needs to be a rule that the autoscanning
script checks for (similar to style issues).
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2011-03-07 20:52 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 ` can we avoid using contractions in GDB messages? Eli Zaretskii
2011-03-07 12:14 ` 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 ` Mike Frysinger [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=201103071552.00959.vapier@gentoo.org \
--to=vapier@gentoo.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