caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Angela Zhu" <angela22.zhu@gmail.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Cancel button or Status bar
Date: Sat, 16 Feb 2008 15:49:35 -0600	[thread overview]
Message-ID: <f82e818a0802161349g7b4e474chfe10d61a54707e79@mail.gmail.com> (raw)
In-Reply-To: <b79ece760802160926k533d8d72ke15c55ad3d57db44@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]

Thanks Dominique!

I was not using threads but I think it is a good idea.

Best regards,
Angela


On Feb 16, 2008 11:26 AM, Dominique Martinet <asmadeus77@gmail.com> wrote:

> Hello,
>
> If it's an OCaml interpreter, I don't think there's a way to evaluate
> the time needed automatically, you can compute the complexity yourself
> and have a rough evaluation of the compile time, but there's no way a
> computer will do it for you without actually evaluating the
> expression.
>
> The stopping is easy though; if you use a GUI you probably already
> have threads (i.e. when you click on run, it will call the "eval
> prog1" function in a thread, so you can keep editing inside of the
> GUI). You can save the thread id when you run it, and ask to kill it
> when you click on the stop button, and I don't even think it will
> raise an exception.
>
> If you're not already using threads, I'm curious and would like to
> know how you plan to handle the GUI.
>
> Regards,
> Martinet Dominique
>
> PS : O'Reilly's book is a nice place to start if you don't know much
> about threads
> http://caml.inria.fr/pub/docs/oreilly-book/html/book-ora175.html
>

[-- Attachment #2: Type: text/html, Size: 1608 bytes --]

  reply	other threads:[~2008-02-16 21:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-16 17:01 Angela Zhu
2008-02-16 17:26 ` [Caml-list] " Dominique Martinet
2008-02-16 21:49   ` Angela Zhu [this message]
2008-02-17 22:03   ` Angela Zhu
2008-02-18  8:24     ` Dominique Martinet

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=f82e818a0802161349g7b4e474chfe10d61a54707e79@mail.gmail.com \
    --to=angela22.zhu@gmail.com \
    --cc=caml-list@inria.fr \
    /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).