Re: strange mkstemp! behavior

[Marius Vollmer]

Marius Vollmer <address@hidden> writes:

> Kevin Ryde <address@hidden> writes:
>
>> Marius Vollmer <address@hidden> writes:
>>>
>>> String literals and the the strings returned by
>>> symbol->string would be read-only.
>>
>> SCM_STRING_CHARS barfs on a read-only literal, badly breaking
>> guile-gtk for instance.  It can be updated, but there's likely to be
>> quite a bit of code using SCM_STRING_CHARS just to read.
>
> Oops, right.  I will make string literals writable again, and put a
> big comment on SCM_STRING_CHARS to make them read-only when
> SCM_STRING_CHARS is removed.

I think now that we need to go further, removing read-only strings
altogether until SCM_STRING_CHARS is removed.  A bit sad, but hey.

(The code will remain, but ifdefed out.)