caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Ville-Pertti Keinonen <will@exomi.com>
To: skaller@users.sourceforge.net
Cc: briand@aracnet.com, caml-list@pauillac.inria.fr
Subject: Re: [Caml-list] exene and ocaml ?
Date: Thu, 1 Apr 2004 12:24:48 +0300	[thread overview]
Message-ID: <6C27A642-83BE-11D8-96B0-000393863F70@exomi.com> (raw)
In-Reply-To: <1080807590.13854.260.camel@pelican>


On Apr 1, 2004, at 11:19 AM, skaller wrote:

> Event driven programming model requires manual
> state management. In losing the stack, the most powerful
> structuring tool available to the progammer is lost,
> and the damage is severe. Simple GUI are easy to get going
> but more complex ones are almost impossible to write.

Yes, my "reasonably well" was in the context of current expectations 
and tools.  I'd really love for OCaml to have efficient threading 
(especially if they were implemented using continuations).

I wouldn't use or recommend a massively multithreaded approach unless 
there was a practical and efficient enough environment available.  CML, 
Oz and presumably Felix would be efficient enough in their threading 
concepts, but don't seem to have the real-world practicality of OCaml 
(or mainstream languages).  I'll admit to not having tested Felix yet, 
although I've downloaded it quite some time ago.

> Simple: there is no stack. Event handlers have to return,
> and when they do the stack is lost.

In Brian's specific example as I understood it, this would not be 
relevant.

> Of course, you can partition your global state space
> into objects, but that in no way changes the fact
> the state space is still global.

In this sense, threads are also global state, as would be lazy streams, 
coroutines or whatever means of encapsulating state you use.

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2004-04-01  9:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01  4:08 briand
2004-04-01  7:25 ` Ville-Pertti Keinonen
2004-04-01  8:19   ` skaller
2004-04-01  9:24     ` Ville-Pertti Keinonen [this message]
2004-04-01 14:08       ` skaller
2004-04-11  6:46         ` briand
2004-04-11  8:41           ` skaller
2004-04-11  9:02             ` Richard Jones
2004-04-11  9:26               ` skaller
2004-04-11 13:21           ` Ville-Pertti Keinonen
2004-04-01 14:34       ` skaller
2004-04-02  5:09       ` briand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6C27A642-83BE-11D8-96B0-000393863F70@exomi.com \
    --to=will@exomi.com \
    --cc=briand@aracnet.com \
    --cc=caml-list@pauillac.inria.fr \
    --cc=skaller@users.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).