David Brown wrote:
This kind of design could just as easily be implemented in a
language that has good abstraction and encapsulation.
I find it very informative to read about process-oriented languages,
like Hermes and Erlang. These are languages where messages are sent not
synchronously between objects, but asynchronously between processes
running in (semantically) their own address spaces, with no shared
variables.
No inheritance, as such. No dynamic dispatch you don't arrange for
yourself (i.e., via picking something from a list of connections to
other processes, like a table of function pointers would do in C). Yet
much the same feel of OO, even tho there's none of the usual "OO" sort
of stuff going on.
--
Darren New / San Diego, CA, USA (PST)
"That's pretty. Where's that?"
"It's the Age of Channelwood."
"We should go there on vacation some time."
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
