unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: David Kastrup <dak@gnu.org>
Cc: "Stephen J. Turnbull" <stephen@xemacs.org>, emacs-devel@gnu.org
Subject: Re: Unary /
Date: Thu, 15 Oct 2015 09:31:02 -0400	[thread overview]
Message-ID: <jwvy4f46zbi.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87d1wgwclb.fsf@fencepost.gnu.org> (David Kastrup's message of "Thu, 15 Oct 2015 14:17:04 +0200")

> Ah, so there will not be a lot of legacy code relying on the current
> semantics.  This would be
[...]
> Since there are about a dozen apparently unrelated changes, the question
> is whether anything specifically relied on this change.

I don't remember the specific case that motivated the change.
IIRC I changed it mostly because the limitation was arbitrary (as you
can see in the patch, which doesn't actually change the code).

I didn't know that CL had decided to give a completely different meaning
to the unary / than the natural generalization of the behavior of (/ X1
X2 ... Xn).  It seems backward to me, so I guess my sense of aesthetics
would incite me to simply revert my patch, adding a comment that for the
semantics of the unary / there is a conflict between the natural choice
and CL compatibility.


        Stefan



  reply	other threads:[~2015-10-15 13:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 11:30 Unary / David Kastrup
2015-10-15 11:48 ` Stephen J. Turnbull
2015-10-15 11:54   ` David Kastrup
2015-10-15 12:00   ` Tassilo Horn
2015-10-15 12:17     ` David Kastrup
2015-10-15 13:31       ` Stefan Monnier [this message]
2015-10-15 14:02         ` David Kastrup
2015-10-15 18:45           ` Stefan Monnier
2015-10-15 19:20             ` Paul Eggert
2015-10-15 12:09 ` Andreas Schwab

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=jwvy4f46zbi.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stephen@xemacs.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).