From: "Michaël Grünewald" <michael-grunewald@wanadoo.fr>
To: Berke Durak <berke@altern.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: Two severe limitations in Graphics module
Date: 29 Aug 2002 20:55:17 +0200 [thread overview]
Message-ID: <878z2pwl4a.fsf@ketanu.dyndns.org> (raw)
In-Reply-To: <20020829110615.GB304@gogol>
Berke Durak <berke@altern.org> writes:
> On Wed, Aug 28, 2002 at 08:06:42AM +0200, Michaël Grünewald wrote:
> > 1/You may have two threads, the first will watch the keyboard
> > (wait_next_event), the second will update puzzle tiles positions, both will
> > send events to your main loop, that will process these events.
>
> I will try to do this, thanks. I just tried ocamlsdl (I get a weird
> relocation error at exit) and ocamlsvga (my S3 card isn't fully
> supported), so I have no other choice.
This is just an idea :)
> I don't like threads very much because they are hard to debug with
> ocamldebug, and native threads are not supported under every OS (for
> ex. OpenBSD).
Humm, isn't *everything* hard to debug with a debugger ? I never did use
one, and had ever been happy with `printf' and `flush', and according to
many people, the debugger is to be reserved for `critical' bugs.
Bye !
--
Michaël Grünewald <michael-grunewald@wanadoo.fr> - RSA PGP Key ID: 0x20D90C12
-------------------
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
next prev parent reply other threads:[~2002-08-30 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-27 20:34 [Caml-list] " Berke Durak
2002-08-28 6:06 ` [Caml-list] " Michaël Grünewald
2002-08-29 11:06 ` Berke Durak
2002-08-29 18:55 ` Michaël Grünewald [this message]
2002-09-03 19:58 ` [Caml-list] Graphics and Thread (was: Two severe limitations in Graphics module) Berke Durak
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=878z2pwl4a.fsf@ketanu.dyndns.org \
--to=michael-grunewald@wanadoo.fr \
--cc=berke@altern.org \
--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).