[Caml-list] include path problem: -I +site-lib/lib not working

I'm trying to get Opa compiled, and following the patch here: http://lists.owasp.org/pipermail/opa/2012-March/000955.html However, it doesn't appear to work unless I include the complete path to cryptolib; +site-lib/cryptolib fails. # this dies $ /home/martin/opt/godi/bin/ocamlopt.opt -I +qmltop

Re: [Caml-list] Timing module initializations (working but crashy)

Hi, Kaustuv Chaudhuri mentionned a few things about this issue on IRC. First, one thing I had forgotten in my previous email: I've tried making the functions usual ocaml-callable C functions (with CAML{param,local,return}*) but that didn't change anything. The segfaults still occurs in the exact

Re: [Caml-list] Recursive polymorphic variants

Le 10/04/2012 15:57, David House a écrit : On Tue, Apr 10, 2012 at 2:51 PM, Gabriel Kerneis wrote: Is there any work-around? Depending on your requirements, just wrapping up the recursive copy of [t] in another constructor might do: type t = [ `A of [ `B | `C of t ]] I don't know why your o

Re: [Caml-list] Recursive polymorphic variants

On Tue, Apr 10, 2012 at 2:51 PM, Gabriel Kerneis wrote: > Is there any work-around? Depending on your requirements, just wrapping up the recursive copy of [t] in another constructor might do: type t = [ `A of [ `B | `C of t ]] I don't know why your original example is disallowed. -- Caml-list

[Caml-list] Recursive polymorphic variants

Hi list, why is this definition allowed: type t = [`A of t] but the following one fails: type t = [`A of [t|`B]] Error: The type constructor t is not yet completely defined Is there any work-around? (My actual example is much larger and complex but I think it boils down to this simpl

Re: [Caml-list] Non-blocking IO interface design

On Tue, Apr 10, 2012 at 4:21 AM, Daniel Bünzli wrote: > Anil, > > Thanks for the analysis. > >> The I/O loop is being called twice for the non-blocking version, as it >> receives >> the `Await signal, does the Unix syscall, and then jumps into decode_src. >> Presumably >> a full non-blocking ver

Re: [Caml-list] Non-blocking IO interface design

Anil, Thanks for the analysis. > The I/O loop is being called twice for the non-blocking version, as it > receives > the `Await signal, does the Unix syscall, and then jumps into decode_src. > Presumably > a full non-blocking version would have to register with a select handler if it > gets an