Depends on whether or not you want to help the poor soul trying to code with your class... If you can't instantiate it then you're not going to even try to use it incorrectly.
Definately makes the class easier to use. G. -- Graeme Foster ([EMAIL PROTECTED]) Principal Software Engineer Aston Broadcast Systems Ltd. (http://www.aston.tv) Disclaimer: I really don't have a clue what I'm on about. -----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]]On Behalf Of Jim Arnold Sent: 24 May 2002 16:19 To: [EMAIL PROTECTED] Subject: Re: Should constructors of all static classes be private ? > Absolutely. This is a common pattern. There's no reason to > instantiate it, > so why let someone? 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. ***************************************************************************** The contents of this email and any attachments are confidential. It is intended for the named recipient(s) only. If you have received this email in error please notify the system manager or the sender immediately and do not disclose the contents to any one or make copies. ** eSafe scanned this email for viruses, vandals and malicious content ** ***************************************************************************** You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
