Re: TRM - Morbidity has set in, or not?
Date: Thu, 18 May 2006 17:46:08 +0300
Message-ID: <e4i171$b4l$1_at_emma.aioe.org>
"Marshall" <marshall.spight_at_gmail.com> wrote in message
news:1147962845.780943.244930_at_i40g2000cwc.googlegroups.com...
> David Cressey wrote:
> > "Marshall" <marshall.spight_at_gmail.com> wrote in message
> > news:1147886349.702914.222780_at_38g2000cwa.googlegroups.com...
> > In order to build on the successes that OOP has acheived, the messaging
> > scheme is going to have to go through a profound shift. When people get
> > around to building a better messaging scheme, they will discover that
the
> > fundamental question is: how can objects share data coherently?
> Hmmm. If you mean read-only data, then this is something of an
> implementation detail. If you mean read/write data (often called
> "state") then I think the right answer is externalizing them from
> the object. The separately-manageable database is the right
> answer.
I mean read-write code.
> The problem with OOP is that it sprinkles state all through your
> program, like sprinkling sand into fine machinery. That state
> can't be managed or inspected, except with huge difficulty.
It's like sprinkling oil. Received on Thu May 18 2006 - 16:46:08 CEST