Sealed vs. Private constructor

  • Thread starter Thread starter wiredless
  • Start date Start date
W

wiredless

Hi,

To minimize resource usage on a WinCE app I want to seal classes and methods
that do not get inherited. Is it still good practice to set the class
constructor to private or is it covered by using sealed?
 
They're used for difference scenarios. One prevents object creation, one
prevents inheritance. If you don't want the ctor visible, make it private,
regardless of whether you want to seal the class or not. If you don't want
it to be inheritable, then seal it. The scope of the ctor has no relevence
on it.

-Chris
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

why is sealed and static not possible at the same time? 7
Overloaded constructors vs. Object initializations 13
Delegates with creation time arguments? 1
How to suppress the "new protected member declared in sealed class"? 1
class sealed Point cannot inerhit 3
Deriving a sealed class 8
What replace "this" in static class? 6
Sealed 7

Back
Top