Gabriel Sechan wrote:
Date: Thu, 25 Oct 2007 15:03:53 -0700
From: [EMAIL PROTECTED]
It is more than side-effect free. It is stateless, or more accurately,
"state is isolated". While no panacea, it is kind of a logical extension
of what OO is doing in terms of encapsulating state. The nice thing is
that the language and the developer is consequently very aware of state.
Given that most problems seem to come from state, this seems like a good
thing.
Completely and totally disagree. State does not cause problems- state is
usually the *solution* to problems. The problem comes from not encapsulating
state correctly. The fact that functional programming languages make state and
side effects so difficult to use are one of the reasons they have completely
failed.
There's a reason why the most common design in electrical engineering is the
state machine- its simple, it works well, and it turns hard to impossible
problems into easily solved ones.
And has horrible support in every single programming language. It is
unsupported to such an extent that an external tool exists to get around
the problem:
http://smc.sourceforge.net/
This is something I just don't get.
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
