For example: If it is "Credentials", then I would say that a Message has Credentials, rather than a Message is-a Credential.
If the different actions are related to each other and can benefit from having a common base class, it might make sense to have an abstract base class which has their shared code/interface etc. But that needn't be the same as your Credentials class.
In reply to Re^3: sub classing best practice
by jbert
in thread sub classing best practice
by cLive ;-)
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |