Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #35893
| Path | csiph.com!2.us.feeder.erje.net!feeder.erje.net!1.eu.feeder.erje.net!news.albasani.net!.POSTED!not-for-mail |
|---|---|
| From | Sebastian <nowhere@nirvana.org> |
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: "implements" does not mean "implements" |
| Date | Sat, 12 Nov 2016 11:22:19 +0100 |
| Organization | albasani.net |
| Lines | 30 |
| Message-ID | <o06qgq$ec$1@news.albasani.net> (permalink) |
| References | <implements-20161110014035@ram.dialup.fu-berlin.de> <o03914$18dp$1@gioia.aioe.org> |
| Mime-Version | 1.0 |
| Content-Type | text/plain; charset=windows-1252; format=flowed |
| Content-Transfer-Encoding | 8bit |
| X-Trace | news.albasani.net SuobS5R29nu6Cgc/lJGIF+/1xaiPMg6AAmuwA/EiL6JAeFnHjWz3+5IoI54gXcpjYeE9hxgLpFCSt8M5OBveKQ== |
| NNTP-Posting-Date | Sat, 12 Nov 2016 10:22:18 +0000 (UTC) |
| Injection-Info | news.albasani.net; logging-data="C1vF5xuvmyIIaGtEBezPhwHAd375qTu5BrmKpbfjg0J3cm/DJTuFaN5YC6W/gKBvWTr6VaFxUTZgyqastxMseNO0Fj62/rvpmIX28oXyRNe3qqnBmIxPaQZ10SfS17+u"; mail-complaints-to="abuse@albasani.net" |
| User-Agent | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 |
| In-Reply-To | <o03914$18dp$1@gioia.aioe.org> |
| Cancel-Lock | sha1:OG8g1a2OYuhZf3NhjIrOYMHCR8Q= |
| Xref | csiph.com comp.lang.java.programmer:35893 |
Show key headers only | View raw
Am 11.11.2016 um 03:05 schrieb Arne Vajhøj:
> On 11/9/2016 7:45 PM, Stefan Ram wrote:
>> Just a small thought I had on the train today:
>>
>> "implements" does not always mean "implements".
>>
>> For example, this compiles:
>>
>> interface A { void m(); }
>>
>> abstract class C implements A { public abstract void m(); }
>
> This is more terminology than Java.
[snip]
> So m is in some sense present in C even though the
> actual implementation have to be supplied by a
> sub class.
>
> Arne
I like to say that interfaces specify behaviors of objects, not
properties of classes. Saying that C implements A amounts to saying that
any o that is an instance of C behaves like an A. It has nothing to do
with what methods get implemented in C.
I would agree that this is terminological hairsplitting without
relevance to Java.
-- Sebastian
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: "implements" does not mean "implements" Arne Vajhøj <arne@vajhoej.dk> - 2016-11-10 21:05 -0500
Re: "implements" does not mean "implements" Sebastian <nowhere@nirvana.org> - 2016-11-12 11:22 +0100
Re: "implements" does not mean "implements" Arne Vajhøj <arne@vajhoej.dk> - 2016-11-12 08:50 -0500
Re: "implements" does not mean "implements" Sebastian <nowhere@nirvana.org> - 2016-11-13 22:30 +0100
Re: "implements" does not mean "implements" Arne Vajhøj <arne@vajhoej.dk> - 2016-11-14 19:48 -0500
csiph-web