Re: proposal: scm_string2str() and scm_symbol2str()

[stefan]

On Mon, 3 Dec 2001, Dirk Herrmann wrote:

> If there is one global variable scm_c_malloc, then setting it within one
> thread may interfere with another thread that expects scm_c_malloc to be
> set differently.  In other words, you would have to introduce some locking
> mechanism to guarantee that the sequence of setting scm_c_malloc and
> calling scm_string2str can not be interrupted by a different thread that
> sets scm_c_malloc to a different value.

This is true.  But in fact (in usual programming pratice) an application
will not use different malloc()s (or should not).  I wonder if we really
should take this very special case which you described into account.

Cheers,
        address@hidden