From: Alex <agrambot@gmail.com>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 35c893d 2/2: Move gensym to core Elisp
Date: Thu, 28 Sep 2017 01:05:29 -0600 [thread overview]
Message-ID: <87y3ozs3pi.fsf@lylat> (raw)
In-Reply-To: <20170913125023.GA26999@holos.localdomain> (Mark Oteiza's message of "Wed, 13 Sep 2017 08:50:23 -0400")
Mark Oteiza <mvoteiza@udel.edu> writes:
> On 13/09/17 at 08:40am, Stefan Monnier wrote:
>> > According to [1] (page 53), MACLISP didn't have a visible
>> > gensym-counter, and instead used an integer argument to gensym to allow
>> > programs to set an internal counter. According to [2], it was only
>> > decided in 1989 to have *gensym-counter* in CL, so before then having an
>> > integer argument made sense if you wanted to manipulate the gensym
>> > state.
>
> Thanks for digging that up.
>
>> > but I wonder if people who use an integer argument here are the type
>> > of people to use `cl' instead of `cl-lib'.
>>
>> I think using the plural here is rather optimistic. I'd already be
>> surprised if there's even just one user of that functionality.
>
> Only one way to find out! I suppose I'll apply the patch I sent earlier.
It doesn't really matter, but wouldn't it be a bit nicer if cl-gensym
and gensym shared the same counter and default prefix?
prev parent reply other threads:[~2017-09-28 7:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170912151313.7686.92637@vcs0.savannah.gnu.org>
[not found] ` <20170912151315.C449D2087D@vcs0.savannah.gnu.org>
2017-09-12 16:48 ` [Emacs-diffs] master 35c893d 2/2: Move gensym to core Elisp Stefan Monnier
2017-09-12 17:21 ` Mark Oteiza
2017-09-12 17:35 ` Mark Oteiza
2017-09-12 18:28 ` Stefan Monnier
2017-09-12 18:51 ` Mark Oteiza
2017-09-13 3:48 ` Alex
2017-09-13 12:40 ` Stefan Monnier
2017-09-13 12:50 ` Mark Oteiza
2017-09-28 7:05 ` Alex [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
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=87y3ozs3pi.fsf@lylat \
--to=agrambot@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mvoteiza@udel.edu \
/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).