From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: [PATCH] Raise an error when detecting old-style backquotes.
Date: Sun, 08 Oct 2017 15:14:01 -0400 [thread overview]
Message-ID: <jwvvajpbgn3.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: CAArVCkSFALZmtHGZq3Awj4-Sk-b+CAFHGVCkJ5pX9GDKn939Bw@mail.gmail.com
>> I don't think it'll make any real difference: in both cases the old code
>> won't work anymore: I'm hard pressed to think of a scenario where the
>> "subtle" behavior change is subtle enough not to be detected
>> fairly quickly.
> For example, code such as '(` foo) would change behavior. Whether a certain
> list is nested or not is definitely subtle enough.
But this is not a complete scenario. You'd need to give additional
context:
- why is there '(` foo) in the source code (it seems already contrived)?
- How is the result used (it's important that the result be
used in a way which works differently but without signaling an error
in both cases)?
Stefan
next prev parent reply other threads:[~2017-10-08 19:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 13:51 Old-style backquotes Philipp Stephani
2017-10-03 14:12 ` Paul Eggert
2017-10-03 14:17 ` [PATCH] Raise an error when detecting old-style backquotes Philipp Stephani
2017-10-03 17:43 ` Stefan Monnier
2017-10-03 18:36 ` Philipp Stephani
2017-10-03 18:52 ` Stefan Monnier
2017-10-08 16:03 ` Philipp Stephani
2017-10-08 19:14 ` Stefan Monnier [this message]
2017-10-04 14:12 ` Richard Stallman
2017-10-04 15:30 ` Stefan Monnier
2017-10-05 7:03 ` Richard Stallman
2017-10-06 4:04 ` Stefan Monnier
2017-10-06 15:17 ` Richard Stallman
2017-10-03 15:02 ` Old-style backquotes Eli Zaretskii
2017-10-08 14:58 ` Philipp Stephani
2017-10-08 16:05 ` Eli Zaretskii
2017-10-08 16:09 ` Eli Zaretskii
2017-10-08 16:25 ` Philipp Stephani
2017-10-08 16:38 ` Eli Zaretskii
2017-10-08 16:59 ` Philipp Stephani
2017-12-09 20:44 ` Philipp Stephani
2017-12-09 20:48 ` Alan Mackenzie
2017-12-09 20:58 ` Philipp Stephani
2017-12-09 21:05 ` Philipp Stephani
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=jwvvajpbgn3.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--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 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).