>> [...] > > Perhaps the "RandomStressTester" should be made more flexible > > and, instead of a hard-coded "GeneratorsList", accept a list of "enum" > > identifiers. e.g. a list (ASCII file) like: > > MT 3 > > MT_64 3 > > SPLIT_MIX_64 3 > > [etc.] > > where the second columns indicates how many runs to perform for > > this type of RNG. > > [A (mandatory) flag specifying this file would replace the first 2 > > command-line arguments.] > > That would be nice. > > But: > > 1. The GeneratorsList class allows a user to use another list that is on > the Java classpath and test their own generators provided by that list. > That is if I understand how Java can build things using reflection. The > likelihood of ever needing to do this is ... ? (very small)
And they could still do that if they add to the "RandomSource" list... > > 2. The GeneratorsList class can be auto generated from the enum There could be a provided input file, updated whenever "RandomSource" is. One advantage is they we could slightly expand the format to allow e.g.: TWO_CMRES 3 TWO_CMRES() 3 TWO_CMRES(1,2) 3 > I suppose it could be updated to require an input text list (as per your > example) but if called with no arguments it can print out a default text > list using the order of the RandomSource enum. > > Thus it should not need to be modified if more generators are added. I'm not sure I understand here. Gilles >> [...] --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
