----- Original Message ----- From: "Berin Loritsch" <[EMAIL PROTECTED]>
NUnit does this for Assemblies. It is a possibility that does not require any special modifications to the JAR file. Alternatively, we can adopt
the
Phoenix style where everything that is needed is defined in the assembly file.
But NUnit is not a example of best-performance application. Although NUnit and Avalon lives in very different worlds. If this "class checking" occurs while builing an assembly and the results could be serialized for further use, then everybody would be happy (at least me)
Aha! Performance! Before we go down the road to optimizing performance I recommend we try the solution as was laid out. If the evidence is overwhelming, we can start optimization at that time. Remember, premature optimization is the root of all evil.
To be honest, NUnit has satisfactory performance for what it does. Its the balance between perfect and good-enough. Start with the correct logical way of doing things, then worry about optimization.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
