From: David Kastrup <dak@gnu.org>
To: Stephen Berman <Stephen.Berman@gmx.net>
Cc: emacs-devel@gnu.org
Subject: Re: typo in accept-process-output (process.c)
Date: Tue, 07 Aug 2007 13:18:32 +0200 [thread overview]
Message-ID: <86fy2v7fuf.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <87wsw7y5ea.fsf@escher.local.home> (Stephen Berman's message of "Tue\, 07 Aug 2007 13\:02\:05 +0200")
Stephen Berman <Stephen.Berman@gmx.net> writes:
> On Mon, 06 Aug 2007 16:50:45 -0400 Michael Olson <mwolson@gnu.org> wrote:
>
>> Richard Stallman <rms@gnu.org> writes:
>>
>>> So the job only has to be done once, what replacement will people
>>> be happy with? Personally, I think plain "if" would be just fine,
>>> except perhaps to the tediously literal-minded.
>>>
>>> In some cases, just "if" is clear.
>>>
>>> Failing that, "only if". As a last resort, "if and only if"
>>> (yuck).
>>>
>>> Where just "if" is not clear, you need to get creative. Find a
>>> rewrite which is clear. "If and only if" is ok when you need it, but
>>> since it is a bit longer, you might look for a better method.
>>
>> The conditionals "only if" and "if" are both unidirectional, whereas "if
>> and only if" is bidirectional. If you want to preserve the logic, it is
>> best to change "iff" to "if and only if". It's not nearly as gross as
>> changing the meaning would be.
>
> The logic textbook by Kalish and Montague uses "`exactly on condition
> that', and sometimes `just in case', as stylistic variants of `if and
> only if'."
"just in case" is pretty much the worst replacement since it has a
well-established colloquial meaning of "as a precaution against the
improbable event of".
--
David Kastrup
next prev parent reply other threads:[~2007-08-07 11:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 12:04 typo in accept-process-output (process.c) Dieter Wilhelm
2007-08-05 12:21 ` David Kastrup
2007-08-05 20:01 ` Glenn Morris
2007-08-05 22:54 ` Dieter Wilhelm
2007-08-06 0:06 ` Nick Roberts
2007-08-06 6:41 ` Dieter Wilhelm
2007-08-06 14:19 ` Richard Stallman
2007-08-06 20:50 ` Michael Olson
2007-08-07 11:02 ` Stephen Berman
2007-08-07 11:18 ` David Kastrup [this message]
2007-08-07 11:31 ` Jason Rumney
2007-08-07 16:37 ` Stefan Monnier
2007-08-07 17:33 ` Drew Adams
2007-08-07 22:01 ` Dieter Wilhelm
2007-08-07 22:17 ` Lennart Borgman (gmail)
2007-08-07 23:16 ` Drew Adams
2007-08-08 0:06 ` Jason Rumney
2007-08-08 0:21 ` Drew Adams
2007-08-09 0:07 ` Richard Stallman
2007-08-08 3:06 ` Eli Zaretskii
2007-08-08 5:50 ` Dieter Wilhelm
2007-08-08 18:43 ` Eli Zaretskii
2007-08-08 20:14 ` David Kastrup
2007-08-08 20:24 ` Stefan Monnier
2007-08-08 20:27 ` martin rudalics
2007-08-08 20:53 ` Stefan Monnier
2007-08-12 20:33 ` Christian Schlauer
2007-08-12 22:01 ` Stephen Berman
2007-08-13 5:00 ` Richard Stallman
2007-08-05 20:54 ` Richard Stallman
2007-08-08 7:54 ` Glenn Morris
2007-08-09 0:07 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86fy2v7fuf.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--cc=Stephen.Berman@gmx.net \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.