[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: strange mkstemp! behavior
From: |
Paul Jarc |
Subject: |
Re: strange mkstemp! behavior |
Date: |
Wed, 22 Sep 2004 12:11:57 -0400 |
User-agent: |
Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux) |
Marius Vollmer <address@hidden> wrote:
> 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?
If symbol->string strings are read-only, and if literals are processed
by (symbol->string (string->symbol foo)), then we get shared storage
for literals too, reducing memory usage. Do we care about making them
non-"eq?"?
paul
- 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 <=
- 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