Patrick Casey <patcasey <at> adelphia.net> writes: > > This is fine until we need a subclass extending AbstractEngine that > > still keeps some methods abstract. Then we'll have trouble naming > > that subclass because they're abstract too. > > AbstractEngine > AbstractDieselEngine > AbstractTurbineEngine > AbstractPistonEngine > > .... > > At least that's the convention I generally go with.
What if later you have a DieselEngine class (probably implementing AbstractDieselEngine), how can you tell the semantic difference between the two? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
