GNU bug report logs - #31718
26.1; Strange behavior of `cond'

Previous Next

Full log

Message #44 received at 31718 <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> gmail.com>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: Robert Cochran <robert-emacs <at> cochranmail.com>,
 Jay Kamat <jaygkamat <at> gmail.com>, Ikumi Keita <ikumi <at> ikumi.que.jp>,
 Héctor Enríquez Ramón <hector.e.r <at> gmail.com>,
 Vibhav Pant <vibhavp <at> gmail.com>, "Basil L.
 Contovounesios" <contovob <at> tcd.ie>, 31718 <at> debbugs.gnu.org,
 Pierre Téchoueyres <pierre.techoueyres <at> free.fr>,
 Andreas Schwab <schwab <at> suse.de>, Eli Zaretskii <eliz <at> gnu.org>
Subject: Re: bug#31718: 26.1; Strange behavior of `cond'
Date: Sat, 16 Jun 2018 11:23:33 -0400

Paul Eggert <eggert <at> cs.ucla.edu> writes:

> A small problem: gensym does not guarantee that the resulting symbol
> is unique so the generated symbol could in theory appear in the input

What?

    gensym is a compiled Lisp function in ‘subr.el’.

    (gensym &optional PREFIX)

    Return a new uninterned symbol.
             ^^^

How could a new symbol have already appeared in the input?

(I have no objection to the alternative you used, just wondering why
gensym is not also correct)

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.