I prefer that my inheritance tree go from the most generic to the most application specific, so inheriting from a class whose method(s) will only be used while the wind is out of the south on leap day if it's Tuesday and the moon is new seems much closer to evil than can().
In reply to Re: OO design: abstract class or can()?
by gloryhack
in thread OO design: abstract class or can()?
by perrin
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |