----- Original Message ----- From: "Leo Sutic" <[EMAIL PROTECTED]>
NH> What happened to the XP voices in Avalon. NH> Value; SIMPLICITY
hammet> I tried to say that too.. :-(
As my finger moves toward the delete key the code screams "Don't delete me! I'm simple!".
I reply "Yes you are simple now, but will you be simple in one year?"
And the code is silent...
:-p
My point is: attributes are nice, they're the best way of association of meta-data instead of xml files or other approach. My objection is for checking every single class in the classpath to see if some of the supports a specific attribute. Even if you could check just a package and childs still a bizarre strategy and bests solutions should exist (no, I don't see any right now, but should exists :-)
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.
Attributes are not going to solve all assembly time problems, but they get us past the important issues (accounting for inter-component dependencies).
--
"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]
