Path: csiph.com!news.mixmin.net!newsreader4.netcologne.de!news.netcologne.de!.POSTED.xdsl-84-44-158-142.netcologne.de!not-for-mail
From: Patrick Roemer <sangamon@netcologne.de>
Newsgroups: comp.lang.java.programmer
Subject: Re: double == double
Date: Tue, 18 Oct 2016 18:55:21 +0200
Organization: news.netcologne.de
Distribution: world
Message-ID: <nu5k5q$a8e$1@newsreader4.netcologne.de>
References: <double-20161012130409@ram.dialup.fu-berlin.de> <ntledh$lfi$1@dont-email.me> <8737k0qd38.fsf@golem.phantasia.org> <87zim5es30.fsf@golem.phantasia.org> <nttf6l$nml$1@gioia.aioe.org> <ntu9de$6uj$1@dont-email.me> <ntuhmi$cdr$1@gioia.aioe.org> <ntuntn$slf$2@dont-email.me> <nu00a0$5sj$1@gioia.aioe.org> <nu00ks$edh$5@dont-email.me> <nu063a$edp$1@gioia.aioe.org> <nu075n$4cs$1@dont-email.me> <nu0bcj$nbt$1@gioia.aioe.org> <nu0dsb$kv3$3@dont-email.me> <nu0g1b$vt5$2@gioia.aioe.org> <nu0qtc$eiu$1@dont-email.me> <nu1e88$9gn$1@gioia.aioe.org> <be7ba475-196e-4269-8b6e-e4a88f8305f1@googlegroups.com> <nu30a0$j0r$1@newsreader4.netcologne.de> <nu382t$pf6$1@dont-email.me> <nu3eq2$tv6$1@newsreader4.netcologne.de> <nu3gr1$8g8$2@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 18 Oct 2016 16:55:22 +0000 (UTC)
Injection-Info: newsreader4.netcologne.de; posting-host="xdsl-84-44-158-142.netcologne.de:84.44.158.142"; logging-data="10510"; mail-complaints-to="abuse@netcologne.de"
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.24) Gecko/20100411 Thunderbird/2.0.0.24 Mnenhy/0.7.6.0
X-Mozilla-News-Host: news://news.netcologne.de
In-Reply-To: <nu3gr1$8g8$2@dont-email.me>
Xref: csiph.com comp.lang.java.programmer:35810

Responding to 4ndre4:
> The problem is where encapsulation stops. If you have a class C 
> containing data D and methods M that act on those data:
> 
> C:
>     D
>     M(D)
> 
> within C you have the same problem: a procedural model.
> 
> This is what happens in many OO languages and it's accepted as normal.

It should rather be: C holds a reference to another object D, and its
methods trigger sending messages to D. There still is (or at least can
be) encapsulation of D's state, and, as opposed to the procedural
approach, there's late binding - the behavior invoked by a message send
depends on the type and state of D. As shown in the Smalltalk/Scala/Ruby
examples, the illusion of OO-ness can be maintained down to primitives
like doubles. There is no data, it's objects all the way down. ;)

Best regards,
Patrick