Jim Arnold [mailto:[EMAIL PROTECTED]] wrote:
> OTOH, why not? It's just more code to write, and you can't > actually do anything with an instance of a pure static class, > not even call static methods. Sure, there's no *real* harm in leaving it public. However, I think completely conveying the behavioral intentions of the class is more important than saving a couple of keystrokes. =) Later, Drew You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
