[Openmcl-devel] weird random problem
testcase at asu.edu
Tue May 20 10:06:11 PDT 2008
Thank you. This seems to be the cause. Setting swank:*communication-
style* to nil solves this problem as the other communication styles
seem to not be available.
On May 20, 2008, at 3:46 AM, Nikodemus Siivola wrote:
> On Tue, May 20, 2008 at 8:54 AM, Gary Byers <gb at clozure.com> wrote:
>> So, when a thread starts up, its binding of *RANDOM-STATE* is set
>> to some
>> value which returns 91 on the first call to (RANDOM 100). The fact
>> 91 is the value that you get repeatedly when you do something similar
>> under SLIME is likely significant, but it's not clear how. I don't
>> usually use SLIME, but didn't see this behavior with 1.2 on x86-64
>> using something called "SLIME 2008-01-27".
> I bet swank:*communication-style* is :spawn, which (IIRC) means every
> evaluation from a non-repl buffer gets a fresh thread -- and hence a
> consistent *random-state* -- whereas REPL evaluations all happen in
> the same thread (IIRC, again).
> -- Nikodemus
More information about the Openmcl-devel