caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Kakadu <kakadu.hafanana@gmail.com>
To: Caml List <caml-list@inria.fr>
Subject: [Caml-list] Threads in byte code and native code work differently
Date: Thu, 25 Sep 2014 14:26:28 +0400	[thread overview]
Message-ID: <CAGmVoG1CUSobH_kR2+tu7Ep9qshxQOCAPKQT2F2USKnvNRrVmw@mail.gmail.com> (raw)

Hello,

I have demo application [1] which creates OCaml threads and executes
C++ event loop from different libraries. When I compile it to native
code everything is fine but when I create custom bytecode executable
OCaml threads doesn't work.

I have tested it with Qt4, Qt5 and GTK2 and behaviour is same. Can you
explain me what is happening there, please

My OCaml version is 4.01.0


Kind regards,
Kakadu

[1] https://github.com/Kakadu/ocaml-trik/tree/desktop

             reply	other threads:[~2014-09-25 10:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25 10:26 Kakadu [this message]
2014-09-25 11:19 ` Török Edwin
2014-09-25 12:17   ` Gerd Stolpmann

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=CAGmVoG1CUSobH_kR2+tu7Ep9qshxQOCAPKQT2F2USKnvNRrVmw@mail.gmail.com \
    --to=kakadu.hafanana@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).