Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: v_borchert@despammed.com (Volker Borchert)
Newsgroups: comp.lang.java.programmer
Subject: Re: Why only public methods on interfaces?
Date: 8 Apr 2011 02:43:35 GMT
Organization: Private site at Eddersheim, Germany
Lines: 11
Distribution: world
Message-ID: <inlson$se7$1@Gaia.teknon.de>
References: <25875c94-9af2-4d28-976d-2050a738ae2e@n10g2000yqf.googlegroups.com> <inlmpc$9tf$1@dont-email.me>
X-Trace: individual.net 7f8gEYUbdSpnnMK1wakPRQjHei9TGdCiaCUsYzUU4glZjSsH18
Cancel-Lock: sha1:okOdMfVGGZq7eCqNE4Jo2Gr8XNE=
Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:2970

Joshua Cranmer wrote:
> You can use abstract classes where reasonable;

No, you can't, at least in some cases, because Java does not support
multiple inheritance... and there are cases where the memory overhead
of a Delegate is not tolerable.

-- 

"I'm a doctor, not a mechanic." Dr Leonard McCoy <mccoy@ncc1701.starfleet.fed>
"I'm a mechanic, not a doctor." Volker Borchert  <v_borchert@despammed.com>