Re: Mixing OO and DB

From: David Cressey <cressey73_at_verizon.net>
Date: Tue, 12 Feb 2008 17:09:54 GMT
Message-ID: <Cpksj.3347$J93.2144_at_trndny08>


"Patrick May" <pjm_at_spe.com> wrote in message news:m2prv2m7zu.fsf_at_spe.com...
> Bob Badour <bbadour_at_pei.sympatico.ca> writes:
> > Stefan Ram wrote:
> >> Patrick May <pjm_at_spe.com> writes:
> >>
> >>>Thread someThread = new SomeThreadImplementation();
> >>>someThread.run();
> >
> > Which is semantically equal to run(someThread)
>
> Only if the context of the run() function is the same as that of
> the SomeThreadImplementation instance at the time the run() method is
> invoked.
>
> You can't define away the differences between OO and other
> techniques that easily.
>
> >>>Unless you're considering the name of the class and/or the name of
> >>>the method to be data, the message is solely about behavior.
> >
> > The value of the variable, someThread, is data.
>
> It does not, however, enable the type of analysis the orignal
> poster was suggesting might be possible. Because of the OO focus on
> behavior, data-only analysis is not able to provide a full view of an
> OO system.
>

Agreed.

However, it's also the case that you can't provide a full view of an OO system without understanding what's going on inside the capsules. In short, encapsulation interferes with full system understanding. Received on Tue Feb 12 2008 - 18:09:54 CET

Original text of this message