Re: [scala] override optional when superclass method is abstract

Hi Paul,

Paul Phillips wrote:
> That is a good point.  I hope this distinction between implementing and
> overriding an abstract method wanders into the documentation around the
> place where they documented the optionality of "override" without
> providing the reasoning.

Maybe.  (And I don't want to start a long discussion on this!)  This is the common
impossibility of choosing the right level of abstraction for a varied audience:  Given the
higher-than-average* number of corner cases afflicting Scala, to present them all to the
user up-front would probably distract from the main theme of any documentation.

Or to put it another way, I can imagine that you could program in Scala all day every day
for a year without finding the optionality of 'override' useful, so why burden the
programmer with that information whilst they're still learning?  Either way, I don't think
there's a right answer, so it's for the judgement of the author...

Cheers,
Jon

* Though rarely without good reason

--
Jon Pretty | Sygneca Ltd