Joern RENNECKE wrote:
You need to be able to set the value of a parameter over a widely
varying range, what makes you think you can pick two values that
will cover all cases, or 4 or 6 for that matter.
In order to allow to specify the exact size of the pool, you can provide the
source of the library that implements it, and have the application programmer
compile it with a -D flag which determines the desired size of the pool.
This can also be driven by a specs file so that all the programmer does is
supply one option with a numerical parameter during 'linking'.
Right, but 12 separate libraries to accomodae 12 separate values is not a reasonable approach. Expecting people to recompile from sources is also not a reasonable approach in a production environment since such recompilation would require revalidation.
For me, the whole approach is ugly anyway, and I would follow a quite different path, as I have indicated in prior messages.
