From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 7B3487FB0A for ; Tue, 9 Dec 2014 18:31:59 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of kakadu.hafanana@gmail.com) identity=pra; client-ip=209.85.220.49; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="kakadu.hafanana@gmail.com"; x-sender="kakadu.hafanana@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of kakadu.hafanana@gmail.com designates 209.85.220.49 as permitted sender) identity=mailfrom; client-ip=209.85.220.49; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="kakadu.hafanana@gmail.com"; x-sender="kakadu.hafanana@gmail.com"; 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-pa0-f49.google.com) identity=helo; client-ip=209.85.220.49; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="kakadu.hafanana@gmail.com"; x-sender="postmaster@mail-pa0-f49.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AogBALIwh1TRVdwxm2dsb2JhbABZhDAEgwHKRwcWAQEBAQERAQEBAQEGCwsJFC6EGxEdARseAxIQDwIIHgIkAREBBQEiNYgBAQMRsGuDJT0xiy+BbIMFi3IKGScNWYUoAQUOgRiSDIFHBYk/hUmIGoIGjXYSJYENgW+CLDwwgkMBAQE X-IPAS-Result: AogBALIwh1TRVdwxm2dsb2JhbABZhDAEgwHKRwcWAQEBAQERAQEBAQEGCwsJFC6EGxEdARseAxIQDwIIHgIkAREBBQEiNYgBAQMRsGuDJT0xiy+BbIMFi3IKGScNWYUoAQUOgRiSDIFHBYk/hUmIGoIGjXYSJYENgW+CLDwwgkMBAQE X-IronPort-AV: E=Sophos;i="5.07,546,1413237600"; d="scan'208";a="112277903" Received: from mail-pa0-f49.google.com ([209.85.220.49]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 09 Dec 2014 18:31:58 +0100 Received: by mail-pa0-f49.google.com with SMTP id eu11so945003pac.36 for ; Tue, 09 Dec 2014 09:31:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=Uc+1V0dURNn8xiiCx4FBWet/5QUPwL4UGbZOlhY9SRo=; b=nvXwKfb4XQHObegXGXHGr/oiw6+89PKD/VEMXdo/8562O1cHlbePulB2KKltQm2yM2 9ur7UKi97ndW5KFpwz+2CYs02ZKebSJUJSJ7B/Rlf2iXt5hE27ud9Elg+01b9ipUJQLC 4hecvR7a1YVhER5JYY8FcG/rOR0pktjH1VBccHsNIY1DsTT3ltEF3pW13FZqICPwtzXY wq1miNJOaap4fIYs94VriZ/X0cBD9Djs0FjvAoXYeurSxu7hKV0krlB9zugtxZWMXrL6 BZG6vnKX0oz9QIe1ntlFRjdPfYe/TYvmKpUn7hpcqmFtfzW2/mXkD56JUOUvYfDIrZqB hrug== MIME-Version: 1.0 X-Received: by 10.66.65.137 with SMTP id x9mr7673530pas.0.1418146317275; Tue, 09 Dec 2014 09:31:57 -0800 (PST) Received: by 10.70.45.201 with HTTP; Tue, 9 Dec 2014 09:31:57 -0800 (PST) Date: Tue, 9 Dec 2014 20:31:57 +0300 Message-ID: From: Kakadu To: Caml List Content-Type: text/plain; charset=UTF-8 Subject: [Caml-list] React wrappers for C++ code and OCaml threads Hello, I have a C++ code and OCaml one in the same application. Ocaml will spawn many OCaml threads. Also I have global C++ object with a number of fields and I want to catch when these fields' values are changing. On every change I want to emit ocaml-react signal associated with a field. OCaml threads will subscribe to signals and do some work after receiving them. So, the whole app is going to have these threads: 1) C++ thread with Qt event loop 2) OCaml thread with event loop which will monitor changes in global C++ object. Also it will emit OCaml-react signals 3) Many OCaml worker threads which will do something useful. This design is a little bit scary for me. Will it work and can I do something better without abandoning C++ code? Have you ever wrapped C++ objects into OCaml event like I need? Kind regards, Kakadu P.S. My C++ object doesn't have Qt properties with Qt signals, it has only fields. And that s why I need another event loop.