This page contains an archived post to the Design Forum (formerly called the Flexible Java Forum) made prior to February 25, 2002.
If you wish to participate in discussions, please visit the new
Posted by aaaa on November 30, 2001 at 2:46 PM
> > In terms of expressing what the behaviour of a category of objects (the term "class" is a touch loaded),
> > we could say that a Java class requires the programmer to go overboard, since a non-trivial, unambiguous
> > declaration of behaviour can only be made by means of an implementation.
> > On the other hand, a Java inteface is too weak, since the programmer can only declare method signitures
> > (and constants), and no behaviour.
> > Thoughts?
> I'm not sure what Mike is looking for here, but it sure sounds like an abstract class.