From: Ivan Gotovchits <ivg@ieee.org>
To: Richard Neswold <rich.neswold@gmail.com>
Cc: Jeremie Dimino <jdimino@janestreet.com>,
"caml-list\@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] OpenGL and LWT
Date: Mon, 17 Mar 2014 14:32:04 +0400 [thread overview]
Message-ID: <8738ihru8r.fsf@golf.niidar.ru> (raw)
In-Reply-To: <CANhEzE4k5unUmDbT+1GsC8BQnt7LPt2QSdM=_joa6d6BKdETUA@mail.gmail.com> (Jeremie Dimino's message of "Mon, 17 Mar 2014 10:09:26 +0000")
>
> Hello,
>
> What would be the appropriate way to use LWT and LabGL together?
Unfortunately, I don't know how LabGL is organized. If it has an event
loop it will be better to incorporate it into main event loop of lwt, as
it was done for lablgtk. Otherwise, I see several solutions. First, use
Lwt_unix jobs, or, if you find it to tedious, just use an async task
(see Lwt.async). There is no particular reason to use detached threads
because they will be serialized by the big lock.
> You could try to assume that OpenGL calls are fast and perform them
> in the same thread as lwt.
But if the assumption is wrong you're in a big trouble.
--
(__)
(oo)
/------\/
/ | ||
* /\---/\
~~ ~~
...."Have you mooed today?"...
next prev parent reply other threads:[~2014-03-17 10:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 17:37 Richard Neswold
2014-03-17 10:09 ` Jeremie Dimino
2014-03-17 10:32 ` Ivan Gotovchits [this message]
2014-03-17 13:39 ` Rich Neswold
2014-03-17 14:05 ` Daniel Bünzli
2014-03-17 14:13 ` Daniel Bünzli
2014-03-17 22:50 ` Richard Neswold
2014-03-17 23:50 ` Daniel Bünzli
2014-03-19 12:01 ` Rich Neswold
2014-03-17 10:34 ` Török Edwin
2014-03-17 11:01 ` Daniel Bünzli
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=8738ihru8r.fsf@golf.niidar.ru \
--to=ivg@ieee.org \
--cc=caml-list@inria.fr \
--cc=jdimino@janestreet.com \
--cc=rich.neswold@gmail.com \
/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).