Seems easy enough - just read out of
My next idea was to dynamically generate the class during the configuration process. Seems logical and it's not that difficult to do. The problem with *that* approach is that the hardware could be upgraded at some point, and if the chip is changed (from, say, Intel to Athlon), we suddenly have a module returning bogus information.
What about dynamically generating the information each time a method is called? Seems horribly inefficient, since the probability of a cpu upgrade is rather low (relatively speaking).
The best compromise solution I can think of is to dynamically generate the class *once*, when the module is require'd. The file is small enough that the one time read should be negligable from a performance standpoint.
PS - I wouldn't have known about the differences in