Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
[Caml-list] looping recursion
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Corey O'Connor <coreyoconnor@g...>
Subject: Re: [Caml-list] looping recursion
Is the connection due to persistance? 
So given a data structure is persistant across operations, let's say a
stack. Suppose if two threads are working with the same instance of a
data structure. One thread pushes a value onto the stack, the other
does not. Due to persistance the other thread's instance of the stack
is unaffected?


On Fri, 30 Jul 2004 00:42:27 +0200, Alex Baretta <> wrote:
> I didn't understand the connection between multithreading and
> persistence, but it's probably too late and I've been working far too
> much to follow you entirely. Let me just give you a couple eurocents of
> industrial experience: side-effects are utterly bad. My Xcaml
> application server was designed two years ago with one major flaw: one
> global state variable. I'm still fighting with the execution engine to
> take it away, but that won't happen before a major rewrite. I won't by
> imperative programming for anything at all. And, yes, in my company the
> mandated standard for deques is batched queues à la Okasaki.
> Alex
> -------------------
> To unsubscribe, mail Archives:
> Bug reports: FAQ:
> Beginner's list:

-Corey O'Connor

To unsubscribe, mail Archives:
Bug reports: FAQ:
Beginner's list: