RE: Understanding Implements

[Buck Calabro <buck.calabro@xxxxxxxxxxxxxxxxx>]

>Now, the original example will still work, as long as you're passing it an
>F-14 Tomcat, but what happens when you want to hear the sound of a 12
>cylinder Dodge Viper? See the dilemna? In order to accomplish the cast,
>you're going to need to impose an unnecessary object hierarchy upon your
>design where Airplane and Automobile are both subclasses of a more
>generic --most likely abstract-- "NoiseMaker" object.

So "interface" is really a way round the single inheritance restriction?  We
can define "utility" classes that aren't really a subclass of anything else.
Without "interface" we'd be locked in to creating artificial objects to
contain utility classes.

Closer?

Buck
+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---