From: Andreas Schwab <schwab@linux-m68k.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 19208@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
Phillip Lord <phillip.lord@newcastle.ac.uk>
Subject: bug#19208: replace-match unhelpful error message
Date: Sun, 04 Aug 2019 11:18:17 +0200 [thread overview]
Message-ID: <m2o915ffvq.fsf@linux-m68k.org> (raw)
In-Reply-To: <e5164f5d-38ee-660c-39b7-5bd564d587e3@cs.ucla.edu> (Paul Eggert's message of "Sat, 3 Aug 2019 13:22:26 -0700")
On Aug 03 2019, Paul Eggert <eggert@cs.ucla.edu> wrote:
> I learned Leibniz conditionals from the late Val Schorre, who was *really*
> good at programming and programming style: Knuth credits Schorre with the
> invention of goto-less programming in the early 1960s. When I redid your
> patch as a Leibniz conditional, I instantly spotted the bug that it
> introduced. You might give Leibniz conditionals a try, as they help make
> code more readable and reliable when checking for range errors or
> overflow.
Perhaps those that need that construct are not good enough to cope with
natural languages.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2019-08-04 9:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 17:00 bug#19208: replace-match unhelpful error message Phillip Lord
2019-08-03 14:01 ` Lars Ingebrigtsen
2019-08-03 20:22 ` Paul Eggert
2019-08-03 20:31 ` Lars Ingebrigtsen
2019-08-03 20:50 ` Paul Eggert
2019-08-04 9:09 ` Andreas Schwab
2019-08-03 23:59 ` Noam Postavsky
2019-08-04 9:02 ` Andreas Schwab
2019-08-04 14:12 ` Noam Postavsky
2019-08-04 15:13 ` Andreas Schwab
2019-08-04 17:41 ` Paul Eggert
2019-08-04 18:14 ` Andreas Schwab
2019-08-05 2:25 ` Richard Stallman
2019-08-04 11:47 ` Lars Ingebrigtsen
2019-08-04 9:18 ` Andreas Schwab [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=m2o915ffvq.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=19208@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=larsi@gnus.org \
--cc=phillip.lord@newcastle.ac.uk \
/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.