Oh, thought you said that - that was a pretty twisted thread.  :-)

Yeah, being liberal with "extend."  You can use the methods of a final class
if the access identifiers make them available.

Cheers!
Mark

----- Original Message -----
From: "Milt Epstein" <[EMAIL PROTECTED]>
Sent: Thursday, June 28, 2001 5:54 PM


> On Thu, 28 Jun 2001, Mark Galbreath wrote:
>
> > Interesting conversation....
> >
> > BTW: a class cannot be both final and abstract.  You can instantiate
>
> Yes, Pier just said that (although I'd more say that it doesn't make
> sense to do it as opposed to you cannot do it; but in the Java way,
> apparently the compiler will catch such a thing).
>
> > a final class; you cannot instantiate an abstract class.  You can
> > override/overload the methods of an abstract class; you cannot with
> > a final class.  You can extend either.
> [ ... ]
>
> Isn't extending the same as overriding/overloading (when it comes to
> when you can/cannot do it)?  That is, the way you override/overload a
> class is by extending it; hence there's no need to talk about them
> separately.  And final classes cannot be extended.

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

Reply via email to