>>Save() was merely used by me as an example of Method Overloading. Some developers add certain methods and properties to all their classes as part of their homemade (attempt for a) framework.
>
>understood.
>
>Not considering how and where you would implement save() still such a button would get concrete as soon as the form it's on is a concrete form. And if there is no code or anything added or implemented in that button on that way of subclassing, it's nevertheless a concrete button. If there would need to be somthing implemented which, when missing will cause errors, it will cause errors, then it's an error of usage. But it's not an error of the class to instanciate then.
If my idea is correct that a class is abstract as long as it is incomplete, even if it is concrete in the eye of the developer (or for example, if it is on a form), then an abstract class on another class has not necessarilly become concrete. Even a form (an .scx) is then abstract as long as it still misses crucial information.
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
