From: Davis Herring <herring@lanl.gov>
To: Drew Adams <drew.adams@oracle.com>, Eli Zaretskii <eliz@gnu.org>,
Paul Pogonyshev <pogonyshev@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Arbitrary function: find the number(s) of expected arguments
Date: Mon, 18 Apr 2016 12:43:54 -0600 [thread overview]
Message-ID: <57152AEA.10006@lanl.gov> (raw)
In-Reply-To: <cbe885f2-7820-40d6-9622-f13b2343e8b5@default>
[I'm back from vacation; a few already-old threads caught my eye.]
> Any existing code that depends on an error being raised by
> `subr-arity' would break. E.g.,
>
> (condition-case err
> (subr-arity 'foo)
> (error (do-something)))
This issue is that of undefined behavior: is (subr-arity 0) UB or is it
defined to be an error? The doc string says simply "SUBR must be a
built-in function." which is language typical of UB in some contexts,
but Emacs doesn't explicitly have that notion to my knowledge.
If it's UB, then your example is wrong already and its breakage is
irrelevant. If the error is a defined part of the interface, then yes
the change is incompatible. All kinds of interfaces are thoroughly
defined only for a subset of cases, and it's as much as anything a
cultural issue whether the (historical) implementation's behavior
outside that set is sacrosanct or not.
Davis
--
This product is sold by volume, not by mass. If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.
next prev parent reply other threads:[~2016-04-18 18:43 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 18:48 Arbitrary function: find the number(s) of expected arguments Paul Pogonyshev
2016-03-15 22:45 ` Davis Herring
2016-03-16 7:41 ` Paul Pogonyshev
2016-03-19 12:26 ` Paul Pogonyshev
2016-03-19 13:10 ` Eli Zaretskii
2016-03-19 13:42 ` Paul Pogonyshev
2016-03-19 13:54 ` Michael Heerdegen
2016-03-19 14:08 ` Eli Zaretskii
2016-03-19 15:20 ` Michael Heerdegen
2016-03-19 15:43 ` Eli Zaretskii
2016-03-19 15:57 ` Michael Heerdegen
2016-03-19 16:24 ` Eli Zaretskii
2016-03-19 17:43 ` Michael Heerdegen
2016-03-19 17:50 ` Eli Zaretskii
2016-03-19 17:59 ` Michael Heerdegen
2016-03-19 18:14 ` Eli Zaretskii
2016-03-19 16:14 ` Philipp Stephani
2016-03-19 16:27 ` Michael Heerdegen
2016-03-19 16:27 ` Eli Zaretskii
2016-03-19 16:30 ` Philipp Stephani
2016-03-19 16:32 ` Eli Zaretskii
2016-03-19 16:34 ` Philipp Stephani
2016-03-19 16:46 ` Philipp Stephani
2016-03-19 16:47 ` Eli Zaretskii
2016-03-19 17:16 ` Philipp Stephani
2016-03-19 17:48 ` Eli Zaretskii
2016-03-19 17:49 ` Philipp Stephani
2016-03-19 18:11 ` Eli Zaretskii
2016-03-19 18:35 ` Michael Heerdegen
2016-04-18 23:02 ` Davis Herring
2016-03-19 19:52 ` Stefan Monnier
2016-03-19 20:33 ` Eli Zaretskii
2016-03-19 22:43 ` Stefan Monnier
2016-03-26 15:55 ` Elias Mårtenson
2016-03-26 17:20 ` Stefan Monnier
2016-03-19 14:26 ` Philipp Stephani
2016-03-19 16:51 ` Paul Pogonyshev
2016-03-19 18:09 ` Eli Zaretskii
2016-03-19 19:32 ` Michael Heerdegen
2016-03-19 19:39 ` Eli Zaretskii
2016-03-19 20:59 ` Michael Heerdegen
2016-03-21 18:36 ` Paul Pogonyshev
2016-03-25 8:44 ` Eli Zaretskii
2016-03-25 16:16 ` Paul Pogonyshev
2016-03-25 16:35 ` Drew Adams
2016-03-25 17:16 ` Paul Pogonyshev
2016-03-25 18:19 ` Drew Adams
2016-03-25 18:28 ` Clément Pit--Claudel
2016-03-25 18:51 ` Use plain-text for mail [was: Arbitrary function: find the number(s) of expected arguments] Drew Adams
2016-03-25 18:57 ` Use plain-text for mail [ Lars Magne Ingebrigtsen
2016-03-25 19:49 ` Andreas Schwab
2016-03-26 1:12 ` Use plain-text for mail [was: Arbitrary function: find the number(s) of expected arguments] Yuri Khan
2016-03-25 17:39 ` Arbitrary function: find the number(s) of expected arguments Eli Zaretskii
2016-03-25 18:31 ` Drew Adams
2016-03-26 8:27 ` Eli Zaretskii
2016-03-26 11:42 ` Paul Pogonyshev
2016-04-02 9:48 ` Eli Zaretskii
[not found] ` <<83y49e731p.fsf@gnu.org>
2016-03-19 19:21 ` Drew Adams
2016-04-18 18:43 ` Davis Herring [this message]
2016-03-16 3:47 ` Stefan Monnier
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=57152AEA.10006@lanl.gov \
--to=herring@lanl.gov \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=pogonyshev@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 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.