On Mon, Jun 27, 2011 at 03:05:36PM +0100, Hans-Peter Diettrich wrote:
> > OOP is just a convenient abstraction, it's for people needed only :)
>
> OOP is for designers, not for hackers ;-)
>
> When some thread-safe code must never bring a program (automaton,
> system...) into an inconsistent state, objects are fine to break down
> the entire program into self-contained sub-systems. This allows to
> dramatically reduce the degree of freedom of the entire ("flattened")
> problem. Whatever can be done entirely inside an object, deserves no
> further consideration of everything outside the object.
Are you talking about monitors? How else will you force an object with only
one thread in it?
Or are you meaning thread+TLS+state exclusively used in the thread as
object?
I've been following this subthread for a couple of posts yet, and the whole
picture leaves an vague feeling.
--
_______________________________________________
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
