set-thread-vm!

set-thread-vm!

[Andy Wingo]

Hi Ludo,

What's the purpose of set-thread-vm! ? I can't think of many coherent
uses it could have, without having the ability to switch a thread from
one vm to another.

A
-- 
http://wingolog.org/

Re: set-thread-vm!

[Ludovic Courtès]

Hello!

Andy Wingo <wingo@pobox.com> writes:

> What's the purpose of set-thread-vm! ?

See commit 639b2eb7107b26207d13bb8acb4c1d38d7dba3bd : it is used to work
around that fact that ‘scm_call_N’ uses whatever ‘scm_the_vm’ returns,
which may be different from the calling VM.

Perhaps that would be better solved by having ‘the-vm’ be a real fluid,
though.

Thoughts?

Thanks,
Ludo’.

Re: set-thread-vm!

[Andy Wingo]

Hi :)

On Sat 25 Sep 2010 23:49, ludo@gnu.org (Ludovic Courtès) writes:

> Andy Wingo <wingo@pobox.com> writes:
>
>> What's the purpose of set-thread-vm! ?
>
> See commit 639b2eb7107b26207d13bb8acb4c1d38d7dba3bd : it is used to work
> around that fact that ‘scm_call_N’ uses whatever ‘scm_the_vm’ returns,
> which may be different from the calling VM.
>
> Perhaps that would be better solved by having ‘the-vm’ be a real fluid,
> though.
>
> Thoughts?

I removed these accessors, because they're not really threadsafe, and
they don't work in the way you expect. We should probably also exclude
multiple threads from using the same VM.

Anyway now there is call-with-vm, which I believe does what you want it
to do. Does that work for you?

Cheers,

Andy
-- 
http://wingolog.org/

Re: set-thread-vm!

[Ludovic Courtès]

Hi!

Andy Wingo <wingo@pobox.com> writes:

> On Sat 25 Sep 2010 23:49, ludo@gnu.org (Ludovic Courtès) writes:
>
>> Andy Wingo <wingo@pobox.com> writes:
>>
>>> What's the purpose of set-thread-vm! ?
>>
>> See commit 639b2eb7107b26207d13bb8acb4c1d38d7dba3bd : it is used to work
>> around that fact that ‘scm_call_N’ uses whatever ‘scm_the_vm’ returns,
>> which may be different from the calling VM.
>>
>> Perhaps that would be better solved by having ‘the-vm’ be a real fluid,
>> though.
>>
>> Thoughts?
>
> I removed these accessors, because they're not really threadsafe, and
> they don't work in the way you expect. We should probably also exclude
> multiple threads from using the same VM.
>
> Anyway now there is call-with-vm, which I believe does what you want it
> to do. Does that work for you?

Yes, perfect!

(And it even does more, which looks nice.  :-))

Thanks,
Ludo’.