[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: strange mkstemp! behavior
From: |
Marius Vollmer |
Subject: |
Re: strange mkstemp! behavior |
Date: |
Wed, 22 Sep 2004 22:28:12 +0200 |
User-agent: |
Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) |
Stephen Compall <address@hidden> writes:
> Marius Vollmer <address@hidden> writes:
>
>> It is very easy now to implement read-only strings in Guile. Should
>> we do so? String literals and the the strings returned by
>> symbol->string would be read-only. Anything else?
>
> - procedure: vector-set! vector k obj
Yeah, right, that can come later. But are there any other read-only
strings that we need to implement?
Actually, I'm now a bit in favor to leave the result of symbol->string
as copy-on-write. It is a useful extension andjust as efficient as a
read-only string.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
- strange mkstemp! behavior, Maarten Grachten, 2004/09/13
- Re: strange mkstemp! behavior, rm, 2004/09/13
- Re: strange mkstemp! behavior, Maarten Grachten, 2004/09/13
- Re: strange mkstemp! behavior, Stephen Compall, 2004/09/13
- Re: strange mkstemp! behavior, Paul Jarc, 2004/09/22
- Re: strange mkstemp! behavior, Kevin Ryde, 2004/09/25
- Re: strange mkstemp! behavior, Marius Vollmer, 2004/09/28
- Re: strange mkstemp! behavior, Marius Vollmer, 2004/09/29