Uhm, I still don't get it. I tried your example on two platforms
yesterday (Mac and Windows -- my Linux machine is 64-bit) and the
numbers are random -- with the exception of the first one (which you can
get around by just having an extra, unused "
Std.rand();" in your
code.). Why would you go to all that trouble?
I think we are seeing system dependant issues. I just tried the code from the topic-starting mail on my own Linux box (Studio 64 Debian repositories but the 32 bit version) in the Mini and to me the first value looks just as random as the rest. I re-started the VM a few times and re-started the whole Mini a few times as well and I don't think it ever started with the same number twice.
Based on that I wouldn't rule out the possibility that Jacob does have a real issue.
Additionally, at the risk of sounding sentimental, to me it seems slightly odd to have a "strongly timed" language that can't read the system time. Aside from ChucKoo clocks and getting around non-random randomness I don't yet have a urgent need for it but there's a sort of aching feeling in the back of my mind that it should be there.... :¬)
Oh... I just noticed that on some level it's already there;
[chuck]:(2:SYSTEM): setting log level to: 2 (SYSTEM)...
[chuck]:(2:SYSTEM): -------( Wed Nov 21 00:32:44 2007 )-------
[chuck]:(2:SYSTEM): starting chuck virtual machine...
Interesting.
Yours,
Kas.