From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id AB1107EFCD for ; Wed, 29 Oct 2014 16:29:33 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of Sebastien.Hinderer@ens-lyon.org) identity=pra; client-ip=140.77.166.138; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="SRS0=MkJL=7U=ens-lyon.org=Sebastien.Hinderer@bounce.ens-lyon.org"; x-sender="Sebastien.Hinderer@ens-lyon.org"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of SRS0=MkJL=7U=ens-lyon.org=Sebastien.Hinderer@bounce.ens-lyon.org) identity=mailfrom; client-ip=140.77.166.138; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="SRS0=MkJL=7U=ens-lyon.org=Sebastien.Hinderer@bounce.ens-lyon.org"; x-sender="SRS0=MkJL=7U=ens-lyon.org=Sebastien.Hinderer@bounce.ens-lyon.org"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of postmaster@sonata.ens-lyon.org designates 140.77.166.138 as permitted sender) identity=helo; client-ip=140.77.166.138; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="SRS0=MkJL=7U=ens-lyon.org=Sebastien.Hinderer@bounce.ens-lyon.org"; x-sender="postmaster@sonata.ens-lyon.org"; x-conformance=sidf_compatible; x-record-type="v=spf1" X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgkCAFsHUVSMTaaKmWdsb2JhbABcg2JYgwbLD4Flhw0WAQEBAQERAQEBAQEICwsHFC6EAwEBAwEjDwFLCwsaAgUTDgICDy0biFEJBbJXlSaBLI51gQWCYTaBHgWWVYcSgTI8iwCFSIVKAQsrIIFba4JLAQEB X-IPAS-Result: AgkCAFsHUVSMTaaKmWdsb2JhbABcg2JYgwbLD4Flhw0WAQEBAQERAQEBAQEICwsHFC6EAwEBAwEjDwFLCwsaAgUTDgICDy0biFEJBbJXlSaBLI51gQWCYTaBHgWWVYcSgTI8iwCFSIVKAQsrIIFba4JLAQEB X-IronPort-AV: E=Sophos;i="5.04,810,1406584800"; d="scan'208";a="85253745" Received: from sonata.ens-lyon.org ([140.77.166.138]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/ADH-AES256-SHA; 29 Oct 2014 16:29:33 +0100 Received: from localhost (localhost [127.0.0.1]) by sonata.ens-lyon.org (Postfix) with ESMTP id C66BA2009C for ; Wed, 29 Oct 2014 16:29:32 +0100 (CET) Received: from sonata.ens-lyon.org ([127.0.0.1]) by localhost (sonata.ens-lyon.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ril5JTB2S2PD for ; Wed, 29 Oct 2014 16:29:32 +0100 (CET) Received: from pema.homeunix.org (unknown [132.227.125.220]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by sonata.ens-lyon.org (Postfix) with ESMTPSA id 955742009B for ; Wed, 29 Oct 2014 16:29:32 +0100 (CET) Received: from seb by pema.homeunix.org with local (Exim 4.84) (envelope-from ) id 1XjVBk-0004uO-2i for caml-list@inria.fr; Wed, 29 Oct 2014 16:29:32 +0100 Date: Wed, 29 Oct 2014 16:29:32 +0100 From: =?utf-8?Q?S=C3=A9bastien?= Hinderer To: caml-list@inria.fr Message-ID: <20141029152932.GE13201@pema> Mail-Followup-To: caml-list@inria.fr References: <20141023121202.GA22996@pl-59055.rocqadm.inria.fr> <20141029143025.GA16501@pema> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Subject: Re: [Caml-list] Filename.temp_dir_name Dear David, Many thanks for your prompt and helpful response. > In batteries[1], see src/batUnix.mliv type [open_flag] which has lines > prefixed ##. There is the program build/prefilter.ml and then a suffix > rule (search for .mliv.mli) in Makefile which generates batUnix.mli. Ah yes, seen, thanks. So this is a line-based approach actually. I'm wondering whether code has already been written implement a block-based approach, i.e. an aproach where one can make several lines compiler-version dependent at once? > In findlib[2], see configure (search for "# bytes?"). It detects > whether bytes.cmi exists in the compiler's lib directory (`ocamlc > -where`/bytes.cmi). Based on that it therefore determines whether it > will generate a dummy META file from the files site-lib-src/bytes or > whether it will compile its compatibility library in src/bytes. Seen also, thanks. I guess it would also be okay,in a tool, to use that same test and to just rpovide the bytes module if it does not exist, rather than installing a package... Thanks! Sébastien.