Ideally you should be able to customize a library to client requirements. That means the ability to add logging if required, and the ability to avoid any performance hit if you don't. That goes for any concern with cross-cuts the library. Tracing, logging, error-handling etc.
The ability to do that in practice is the subject of techniques like template-traits in C++, and Aspect Oriented Programming; indeed the whole Generative Programming movement. In .Net you can get closest to this with events and pluggable interfaces. Peter --- John Lam <[EMAIL PROTECTED]> wrote: > Actually, I'm not sure that I agree that the library should not do *any* > logging. If I want to debug a library in the field, I would want to have > mechanisms whereby I could enable logging in my library (reading a > registry key, presence of an environment variable etc). __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
