On 8 Apr 2012, at 21:37, Daniel Bünzli wrote:
>
> I think that the first five points are mostly met and the
> cps transformation of blocking into non-blocking is relatively
> straightforward and remains readable in my opinion. Regarding the 6th
> point, using the included `setrip.native` program o
On 8 Mar 2012, at 22:26, Sylvain Le Gall wrote:
>
> 2012/3/8 Adrien :
>> Hi,
>>
>> On 08/03/2012, Sylvain Le Gall wrote:
>>> Hi,
>>>
>>> 2012/3/8 Daniel Bünzli :
Le jeudi, 8 mars 2012 ŕ 09:31, Sylvain Le Gall a écrit :
> setup.ml will be enough for me ;-) But I am biased.
Fo
There's a very useful %.pp.ml target in OCamlbuild that runs the source through
camlp4 and outputs the result. This doesn't work when ocamlfind is used, as it
includes the -pp flags within the ocamlfind invocation.
I took a look at adding support for this into ocamlbuild (when -use-ocamlfind
i
On 18 Dec 2011, at 20:01, Benedikt Meurer wrote:
> Am 18.12.2011 um 20:46 schrieb Ashish Agarwal :
>
>> On Sun, Dec 18, 2011 at 4:35 AM, Benedikt Meurer
>> wrote:
>>
>> the OASIS port is named "caml-oasis".
>>
>> Please try to transition to the consistent name OCaml, a decision made at
>> t
I think Ancient is exactly what you're looking for.
Just disable swap (which you should do anyway on a big modern server), and it
will let you keep in-memory, out-of-heap OCaml values that don't get scanned by
the GC.
Anil
On 8 Dec 2011, at 08:19, William Le Ferrand wrote:
> hi Stephane
>
>
On 4 Nov 2011, at 09:24, ri...@happyleptic.org wrote:
> -[ Thu, Nov 03, 2011 at 09:15:57PM +0100, Fabrice Le Fessant ]
>> Hi,
>>
>> By the way, Thomas is also working on a plugin for ocamldoc, with
>> incremental search. An example of what it generates (for the stdlib and
>> some of our inte
icitly part of the pack).
So just try listing all the modules you use explicitly in the .mlpack and
see if the issue goes away.
--
Anil Madhavapeddy http://anil.recoil.org
--
Caml-list mailing list. Subscription management and archives:
https://sympa-roc.inria.fr
en not used on inside those, that would break a lot
of other applications.
Anyhow, directly checking the number is bad for portability reasons as the
ERESTARTNOHAND is a Linux-ism. I'm taking a shot at porting Core/Async to
OpenBSD at the moment, so will patch out that
On 15 Sep 2011, at 11:04, Mehdi Dogguy wrote:
> On 13/09/2011 20:37, ri...@happyleptic.org wrote:
>> The Lwt doc states that you should not use "raise" when using Lwt but
>> use Lwt.fail instead.
>>
>> So, is it still OK to call functions (for instance from the stdlib)
>> that may raise an exce
Yes, it's essential to do this for many common functions such as Hashtbl.find.
The nice thing about Lwt is that you control yielding, so as long as you catch
the exception locally and "convert" it into the Lwt monad, everything works
great.
The occasional exception leak is really hard to track
_obj = !Options.ext_obj in
let x_o = "%"-.-ext_obj in
(* Rule to link a module and output a standalone object file *)
rule "ocaml: cmx* & o* -> .m.o"
~tags:["ocaml"; "native"; "output_obj"]
~prod:"%.m.o"
~deps:["
Is there a built-in rule in ocamlbuild to generate the -output-obj output
instead of a direct link?
I note there are these built-in tags in the ocamlbuild source:
ocaml_specific.ml:flag ["ocaml"; "link"; "native"; "output_obj"]
(A"-output-obj");;
ocaml_specific.ml:flag ["ocaml"; "link"; "byte";
12 matches
Mail list logo