Rob Browning <[EMAIL PROTECTED]> writes:
> Marius Vollmer <[EMAIL PROTECTED]> writes:
>
>> Is there a way to return an exit code with pthread_exit()?
>
> Doesn't pthread allow that directly?
>
> Function: void pthread_exit (void *RETVAL)
>
> Of course you have to pthread_join() to get the value.
Bruce Korb <[EMAIL PROTECTED]> writes:
> It turns out that in all places where I was using scm_makstr(), I
> was also using SCM_CHARS to access the string memory and then fill
> it in. It *must* be safe to do because I don't call any scheme
> functions before I am done scribbling in the memory.
[EMAIL PROTECTED] (Ludovic Courtès) writes:
> See also:
> http://lists.gnu.org/archive/html/guile-devel/2005-10/msg00101.html .
>
>> If you don't want to warning, you can define your own way of handling
>> duplicates. See the NEWS file for docs about the options.
>
> Precisely, you said you were
[EMAIL PROTECTED] (Ludovic Courtès) writes:
> Marius Vollmer <[EMAIL PROTECTED]> writes:
>
>> C code can observe the GC doing its thing (via the smob free
>> functions). In order not to overconstrain the implementation of the
>> GC (which is pretty constrained already anyway), we have the
>> addi
Neil Jerram <[EMAIL PROTECTED]> writes:
> I'm seeing a failure of the test-system-cmds test, and have narrowed
> it down to this:
>
> [EMAIL PROTECTED]:~/guile-cvs-head/guile/guile-core$ ./pre-inst-guile -q
> guile> (exit 42)
> Segmentation fault
>
> Neil
I think I've nailed this. In this
Marius Vollmer <[EMAIL PROTECTED]> writes:
> Neil Jerram <[EMAIL PROTECTED]> writes:
>
>>> However, making the read procedure used by 'load' configurable can't
>>> hurt, I think.
>>
>> OK, thanks. I'll just wait a few days in case you or anyone else have
>> further comments. If not I'll commit t
