From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ivg@ieee.org>
X-Original-To: caml-list@sympa.inria.fr
Delivered-To: caml-list@sympa.inria.fr
Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83])
	by sympa.inria.fr (Postfix) with ESMTPS id 7541E7F860
	for <caml-list@sympa.inria.fr>; Mon, 17 Mar 2014 11:32:13 +0100 (CET)
Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender
  authenticity information available from domain of
  ivg@ieee.org) identity=pra; client-ip=209.85.215.52;
  receiver=mail2-smtp-roc.national.inria.fr;
  envelope-from="ivg@ieee.org"; x-sender="ivg@ieee.org";
  x-conformance=sidf_compatible
Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of
  ivg@ieee.org designates 209.85.215.52 as permitted sender)
  identity=mailfrom; client-ip=209.85.215.52;
  receiver=mail2-smtp-roc.national.inria.fr;
  envelope-from="ivg@ieee.org"; x-sender="ivg@ieee.org";
  x-conformance=sidf_compatible; x-record-type="v=spf1"
Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender
  authenticity information available from domain of
  postmaster@mail-la0-f52.google.com) identity=helo;
  client-ip=209.85.215.52;
  receiver=mail2-smtp-roc.national.inria.fr;
  envelope-from="ivg@ieee.org";
  x-sender="postmaster@mail-la0-f52.google.com";
  x-conformance=sidf_compatible
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqwBAAfOJlPRVdc0lGdsb2JhbABZhx6+e4EaFg4BAQEBBwsLCRIqgiUBAQEDASNWBQsLDgwCBSECAg8BBCABBQEiLodWCAQBpB+MDqITF4EpjT8Hgm+BSQSJTI56kEFBhF8
X-IPAS-Result: AqwBAAfOJlPRVdc0lGdsb2JhbABZhx6+e4EaFg4BAQEBBwsLCRIqgiUBAQEDASNWBQsLDgwCBSECAg8BBCABBQEiLodWCAQBpB+MDqITF4EpjT8Hgm+BSQSJTI56kEFBhF8
X-IronPort-AV: E=Sophos;i="4.97,669,1389740400"; 
   d="scan'208";a="63216750"
Received: from mail-la0-f52.google.com ([209.85.215.52])
  by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 17 Mar 2014 11:32:12 +0100
Received: by mail-la0-f52.google.com with SMTP id ec20so3554708lab.11
        for <caml-list@inria.fr>; Mon, 17 Mar 2014 03:32:12 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to
         :message-id:user-agent:mime-version:content-type
         :content-transfer-encoding;
        bh=keVG2aeDBQUjHQ59Sh9hSBiGG3HaW4frwV540zlXfsc=;
        b=XJcF45rLxR10TIYVD5IstRGLuBwIQ5hc8lpikiFcp+oen01Ut0SHZcj3kLPtu/m/Iu
         9xModd9nGBdphSKWpUt2b8/LBIEkhlTRhEOnPIY5Frb2eANnXL0nsHcary97HpLDIgwu
         CTdKG9IpF61AP9Pi6JCqBMFjJdhoMhuQvWBNGVXAdUAPrt9PDTVhsmU7DMVydqEGJ0MR
         QyEDi10h8QAoC210TkQwgew6yQXclYzAkrltfMvH3UXjveO6MuWKJnkks4PVNAyuc+ST
         Lyy4jIvjjhOTGnLlOIGqtX25mc9iFs1zaRvd1DUzeLyO6CXU0P8W5CUtoj9n5UVX3w/d
         IhGA==
X-Gm-Message-State: ALoCoQkyjtgS2m0GXh1GweN4lu2N/H96o2msINNYPwCbVrSa/9/JMbdIBXmVjq+XZO053bREGpxr
X-Received: by 10.152.18.229 with SMTP id z5mr16489805lad.27.1395052331908;
        Mon, 17 Mar 2014 03:32:11 -0700 (PDT)
Received: from golf.niidar.ru.niidar.ru ([109.188.124.27])
        by mx.google.com with ESMTPSA id cr6sm4718027lbb.19.2014.03.17.03.32.10
        for <multiple recipients>
        (version=TLSv1.1 cipher=RC4-SHA bits=128/128);
        Mon, 17 Mar 2014 03:32:11 -0700 (PDT)
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>
References: <1732E7D3-C154-4305-90C8-0CC292FE08CF@gmail.com>
	<CANhEzE4k5unUmDbT+1GsC8BQnt7LPt2QSdM=_joa6d6BKdETUA@mail.gmail.com>
Date: Mon, 17 Mar 2014 14:32:04 +0400
In-Reply-To: <CANhEzE4k5unUmDbT+1GsC8BQnt7LPt2QSdM=_joa6d6BKdETUA@mail.gmail.com>
	(Jeremie Dimino's message of "Mon, 17 Mar 2014 10:09:26 +0000")
Message-ID: <8738ihru8r.fsf@golf.niidar.ru>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Caml-list] OpenGL and LWT


>
> Hello,
>=20
> 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.=20


> You could try to assume =C2=A0that 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.=20



--=20
         (__)=20
         (oo)=20
   /------\/=20
  / |    ||=20=20=20
 *  /\---/\=20
    ~~   ~~=20=20=20
...."Have you mooed today?"...