doco gensym and uninterneds

doco gensym and uninterneds

[Kevin Ryde]

        * scheme-data.texi (Symbol Primitives): In gensym, cross reference
        uninterned symbols, use @w{} on " g" prefix to avoid any chance of a
        line break obscuring it.

New text:


Uniqueness can be guaranteed by instead using uninterned symbols (*note
Symbol Uninterned::), though they can't be usefully written out and
read back in.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel

Re: doco gensym and uninterneds

[Rob Browning]

Kevin Ryde <user42@zip.com.au> writes:

>         * scheme-data.texi (Symbol Primitives): In gensym, cross reference
>         uninterned symbols, use @w{} on " g" prefix to avoid any chance of a
>         line break obscuring it.
>
> New text:
>
>
> Uniqueness can be guaranteed by instead using uninterned symbols (*note
> Symbol Uninterned::), though they can't be usefully written out and
> read back in.

As I recall when Marius and I talked about this a while back, gensym
hasn't been creating uninterned symbols, but it should be -- this was
a planned fix, and I *think*, but don't have the mail handy, that we
were also thinking of following CL and adding gentemp for unique
symbols.

The screwy names that gensym generates right now were just a quick fix
to try to make it much less likely that we'd cause accidental
collisions until we get a chance to "fix it right".

FWIW

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel

Re: doco gensym and uninterneds

[Kevin Ryde]

Rob Browning <rlb@defaultvalue.org> writes:
>
> As I recall when Marius and I talked about this a while back, gensym
> hasn't been creating uninterned symbols, but it should be -- this was
> a planned fix, and I *think*, but don't have the mail handy, that we
> were also thinking of following CL and adding gentemp for unique
> symbols.

What I should have said was that all I was going to change was the bit
that says,

	The 1.8 release of Guile will include a way of creating
	symbols that are @emph{guaranteed} to be unique.

which I assumed was not updated when uninterned symbols were
introduced.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel