From: Glenn Morris <rgm@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: xfq.free@gmail.com, Eli Zaretskii <eliz@gnu.org>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: trunk r113878: Refine previous change.
Date: Wed, 14 Aug 2013 22:16:31 -0400 [thread overview]
Message-ID: <ap38qbog00.fsf@fencepost.gnu.org> (raw)
In-Reply-To: CAAeL0SRP=Dh77R-CxwK67J2nUFMfebBRwqRgF4e7u7H2PAp=3Q@mail.gmail.com
Juanma Barranquero wrote:
>> These are internal self-defenses of the implementation, we don't
>> expect users to pass such invalid arguments (a.k.a. "undefined
>> behavior") at all.
>
> If they are self defenses, wouldn't be better to signal an error?
I don't think we can go from "this is documented in the manual to work"
to "this is an error" in the space of a day. For now, we can just go to
"this is undocumented", with a view to perhaps making it an error some
years down the line. Cf bug#15059.
> It would break some code, but arguably that code is already broken,
> and silently so.
It's not broken to intentionally make use of documented behaviour,
and we have no way of knowing whether this was being intentionally used
anywhere. (I don't think it matters much.)
next prev parent reply other threads:[~2013-08-15 2:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1V9bet-0004qo-C7@vcs.savannah.gnu.org>
2013-08-14 19:34 ` trunk r113878: Refine previous change Glenn Morris
2013-08-14 19:45 ` Eli Zaretskii
2013-08-14 22:30 ` Xue Fuqiao
2013-08-15 2:18 ` Glenn Morris
2013-08-16 0:22 ` Xue Fuqiao
2013-08-14 23:30 ` Juanma Barranquero
2013-08-15 2:16 ` Glenn Morris [this message]
2013-08-15 12:29 ` Juanma Barranquero
2013-08-15 14:29 ` Stefan Monnier
2013-08-15 15:06 ` Eli Zaretskii
2013-08-15 16:01 ` Glenn Morris
2013-08-15 16:42 ` Stefan Monnier
2013-08-15 17:18 ` Glenn Morris
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=ap38qbog00.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=xfq.free@gmail.com \
/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).