From: David Kastrup <dak@gnu.org>
Cc: Alan Mackenzie <acm@muc.de>, emacs-devel@gnu.org, miles@gnu.org
Subject: Re: English usage bug in bytecomp.el
Date: Tue, 08 Mar 2005 11:33:11 +0100 [thread overview]
Message-ID: <x5r7iqqvfc.fsf@lola.goethe.zz> (raw)
In-Reply-To: <fc339e4a050308015760de2423@mail.gmail.com> (Miles Bader's message of "Tue, 8 Mar 2005 18:57:31 +0900")
Miles Bader <snogglethorpe@gmail.com> writes:
> On Tue, 8 Mar 2005 08:02:35 +0000 (GMT), Alan Mackenzie <acm@muc.de> wrote:
>> [Discussion of "`foo' is an obsolete function since 21.4;"]
>>
>> >I think "is ... since" is pretty common usage actually, and certainly
>> >makes sense.
>>
>> <Gnashes teeth>
>>
>> Yes, it does make sense and it is regrettably common usage, but it is
>> WRONG. It is something that a native English speaker would never say.
>> In this case, it is just as easy to be correct.
>
> Hmm, I'm a native English speaker (and I certainly appreciate fine
> language), but I don't mind this at all. It simply doesn't register
> very high on the "feels wrong" scale, though it does a little.
>
> I also agree with Nick that the "correct" form is less clear (and
> requires a funny little twiddly bit in the code).
>
> However, a variant which might be even clearer, and maybe less
> objectionable would be "FOO is an obsolete function (since 21.4)".
This does not help really. If my language sensors are correct, a
non-objectionable phrasing might be
"As of 21.4, Foo is an obsolete function."
But I still don't see that "has been" is something that even a
non-native speaker has any possibility of avoiding to see quite a lot,
anyhow.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2005-03-08 10:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 20:17 English usage bug in bytecomp.el Alan Mackenzie
2005-03-07 23:09 ` Miles Bader
2005-03-08 8:02 ` Alan Mackenzie
2005-03-08 8:49 ` Nick Roberts
2005-03-08 10:24 ` David Kastrup
2005-03-08 11:45 ` Nick Roberts
2005-03-08 9:57 ` Miles Bader
2005-03-08 10:33 ` David Kastrup [this message]
2005-03-08 15:37 ` John S. Yates, Jr.
2005-03-08 16:08 ` Bill Wohler
2005-03-08 17:26 ` Andreas Schwab
2005-03-08 21:10 ` Nick Roberts
2005-03-08 22:15 ` Miles Bader
2005-03-08 22:36 ` Bill Wohler
2005-03-09 16:59 ` Richard Stallman
2005-03-09 3:12 ` Richard Stallman
2005-03-09 9:49 ` David Kastrup
2005-03-09 10:22 ` Miles Bader
2005-03-08 13:08 ` Stefan Monnier
2005-03-09 3:12 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x5r7iqqvfc.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=miles@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).