curious behavior

[Robert Brenstein]

It is a more elegant way of getting it but the result is the same. 
For whatever reason, if running in a script, the last three digits of 
milliseconds tend to be  000 through 005. Yes, really low numbers. In 
individual calls, any number 000 to 999 seems possible. Weird.

>How about using this?
>
>get milliseconds() mod 1000
>
>Cheers!
>
>Raymond
>
>on 3/6/03 7:57 AM, Robert Brenstein at rjb at rz.uni-potsdam.de wrote:
>
>>  get char -3 to -1 of milliseconds()
>>
>>  gives always 000
>>
>>  however,
>>
>>  put milliseconds() into m
>>  get char -3 to -1 of m
>>
>>  gives the expected variation in value.
>>
>>  This happens only when the code is a part of a script.
>>  From the message box, either variant works same.
>>
>>  A bug or feature?
>>
>>  Robert
>>  _______________________________________________
>>  metacard mailing list
>>  metacard at lists.runrev.com
>>  http://lists.runrev.com/mailman/listinfo/metacard
>
>_______________________________________________
>metacard mailing list
>metacard at lists.runrev.com
>http://lists.runrev.com/mailman/listinfo/metacard