The following command:
For /L %E in (33,-1,30) Do (Echo %E %@Random[0,%@Eval[2**%E-1]])
and its output:
TCC: (Sys) The parameter is incorrect.
"%@Random[0,8589934591]"
TCC: (Sys) The parameter is incorrect.
"%@Random[0,4294967295]"
31 792146758
30 485602801
would seem to indicate that 2**31-1 is the largest value that the @Random function can take as a parameter, which isn't, as far as I can tell, documented.
However, the very similar command:
For /L %E in (33,-1,30) Do (Echo %E %@Random[0,%@Eval[2**%E]])
produces:
33 0
32 0
TCC: (Sys) The parameter is incorrect.
"%@Random[0,2147483648]"
30 704183992
I tend to think that this is, as it says in the subject line, a relatively minor bug given the above...
For /L %E in (33,-1,30) Do (Echo %E %@Random[0,%@Eval[2**%E-1]])
and its output:
TCC: (Sys) The parameter is incorrect.
"%@Random[0,8589934591]"
TCC: (Sys) The parameter is incorrect.
"%@Random[0,4294967295]"
31 792146758
30 485602801
would seem to indicate that 2**31-1 is the largest value that the @Random function can take as a parameter, which isn't, as far as I can tell, documented.
However, the very similar command:
For /L %E in (33,-1,30) Do (Echo %E %@Random[0,%@Eval[2**%E]])
produces:
33 0
32 0
TCC: (Sys) The parameter is incorrect.
"%@Random[0,2147483648]"
30 704183992
I tend to think that this is, as it says in the subject line, a relatively minor bug given the above...