From: Xavier Leroy <xavier.leroy@inria.fr>
To: David MENTRE <dmentre@linux-france.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] How to avoid compiling some code (like #ifdef in C)
Date: Thu, 11 Sep 2003 17:30:56 +0200 [thread overview]
Message-ID: <20030911173056.A29749@pauillac.inria.fr> (raw)
In-Reply-To: <87llswpnvn.fsf@linux-france.org>; from dmentre@linux-france.org on Wed, Sep 10, 2003 at 07:14:04PM +0200
> --begin--
> open Printf
>
> let compile_code = false
>
> let a () = printf "toto\n"
>
> let _ = if compile_code then let t = 1 in a ()
> --end--
>
> In above code, if compile_code is true, then the auto-test is executed,
> otherwise not. But if compile_code is false, is the code corresponding
> to 'let t = 1 in a ()' generated?
With ocamlopt, that code is eliminated as part of constant
propagation.
With ocamlc, the code of "let t = 1 in a()" is generated.
> Does anybody see a better approach to do such a thing?
Others mentioned preprocessing with the tool of your choice. Camlp4
can do #ifdef-style conditional compilation, but in a pinch you can
even use cpp as your preprocessor.
Whether this is a "better" approach is open to debate. With a
preprocessor, you can remove not just code for expressions, but also
other kind of code, e.g. code for the toplevel binding "let a() = ...".
So, you get more flexibility, but at the expense of less static
checking. In particular, code that is #ifdef-ed out is not
type-checked, while it is type-checked in your solution above.
- Xavier Leroy
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-09-11 15:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 17:14 David MENTRE
2003-09-10 17:31 ` Markus Mottl
2003-09-11 15:30 ` Xavier Leroy [this message]
2003-09-11 16:28 ` Richard Jones
2003-09-12 12:15 ` David MENTRE
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=20030911173056.A29749@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=dmentre@linux-france.org \
/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