[4417] in java-interest
Re: interfaces
daemon@ATHENA.MIT.EDU (Ken Arnold - Sun Labs)
Fri Dec 22 15:06:41 1995
Date: Fri, 22 Dec 1995 13:36:00 -0500
From: arnold@suneast.East.Sun.COM (Ken Arnold - Sun Labs)
To: andrewfr@bnr.ca
Cc: java-interest@webrunner.neato.org
>Andrew:
>>Me:
>> A purely abstract class (one that has *only* abstract methods) is hard
>> to distinguish from an interface, but if that's what you're producing,
>> you should produce an interface instead.
>
>A class with all its methods abstract and an interface would look the
>same, but I believe the VM treats things like casting/method lookup
>for classes and interfaces differently.
Absolutely. A class with only abstract methods is *not* an interface.
I said that a class with only abstract methods should have been created
as an interface almost every time.
Ken
-
This message was sent to the java-interest mailing list
Info: send 'help' to java-interest-request@java.sun.com
