The only real reason why I want to override it in the derived class is so
that the method is encapsulated from the implementer with another method
that has a more specific meaning.
Example:
public class ClassA
{
private String _GenericText = "";
public virtual String GenericText
{
get
{
return _GenericText;
}
set
{
_GenericText = value;
}
}
}
public class ClassB : ClassA
{
public ClassB()
{
base.GenericText = "MyText";
}
//
// I want to make GenericText private somehow in here because it has a
wrapper
// with a different name that only returns a read-only constant.
//
// private new GenericText (or something similar)
// get... set...
//
//
public String MyText
{
get
{
return base.GenericText;
}
}
}
I realize this is a crude example, but what I am trying to convey is that I
require the derived class to "hide" the implementation of GenericText
because it contains a wrapper property that is constant and read-only. How
can I "hide" the GenericText property in my derived class?
--
-----------------------------------
Ken Varn
Senior Software Engineer
Diebold Inc.
EmailID = varnk
Domain = Diebold.com
-----------------------------------
"Bjorn Abelli" <bj**********@DoNotSpam.hotmail.com> wrote in message
news:uT**************@TK2MSFTNGP09.phx.gbl...
"Ken Varn" wrote...
Is there anyway to override a public virtual
method or property so that it
is private in my derived class?
What would be the the point in overriding it
at all if you'll just be using it inside that class?
Why not simply use another name for that method?
I tried using new on the property and
making it private, but no luck.
If you have derived from a class, you'll have to see the operations in the
superclass as a "contract" not to be violated. Any operations you can do
on an instance of the superclass, you must be able to do on instances of the
subclasses (Liskov's principle).
Hence, you cannot make an inherited operation more restricted than in the
superclass.
One point of inheritance is the possibility of polymorphism, where you in
some cases don't know if the instance is of the superclass or a derived
class. It must still be able to respond to the operations of the
superclass, regardless if the methods are overridden or not. It's up to the subclasses
if the methods are overridden (with e.g. "empty" methods), but they still
must be able to respond to the operation.
// Bjorn A
