From: Eliot M. <mo...@cs...> - 2012-08-30 13:08:30
|
Here's a wondering: Would it be that much more complicated (or maybe this is what is currently done) to have the notions of: harness benchmark application library where the libraries are things the benchmarks can choose to use (i.e., to have on their class path)? If a library is used by only one benchmark, then it would not matter, though it might be uniform to put a library in the library group rather then the benchmark anyway. But if a library is used by two or more benchmarks, then you would save space. If two benchmarks want different versions of the same library, they could still include the library in the benchmark ... Regards -- Eliot |