is it good design practice to only have a parameterless base class constructor?
Posted
by T. Webster
on Stack Overflow
See other posts from Stack Overflow
or by T. Webster
Published on 2010-03-22T15:01:31Z
Indexed on
2010/03/22
15:11 UTC
Read the original article
Hit count: 309
In base class constructors I always see a parameterless constructor, like so:
public abstract BaseClass {...
protected BaseClass() { }
...}
but is it acceptable design to include a parameter in the base class constructor?
public abstract BaseClass {...
protected BaseClass(string initObj) { }
...}
© Stack Overflow or respective owner
