In a Visual Class Library, if I wanted to create a class, then subclass it twice,
and have a method with the same name in both child classes, I would obviously
create the method in the Parent.
Then all I have to do is open the Visual Class and navigate to the method and add
any code I want.
But in a Programmatic class, if I want to do the same, create a parent with 2 children
and have a method called the same in both children, is there any reason to create
the method in the parent? Why not just create a procedure with the same name in both
child classes?
Everything makes sense in someone's mind
public class SystemCrasher :ICrashable
In addition, an integer field is not for irrational people