From: Kenneth Knowles <kknowles@berkeley.edu>
To: Richard Jones <rich@annexia.org>
Cc: caml-list@pauillac.inria.fr
Subject: [Caml-list] Conditional Compilation (was mod_caml Makefile)
Date: Fri, 16 Apr 2004 10:27:26 -0700 [thread overview]
Message-ID: <20040416172726.GC27407@tallman.kefka.frap.net> (raw)
In-Reply-To: <20040416171708.GA29995@redhat.com>
On Fri, Apr 16, 2004 at 06:17:08PM +0100, Richard Jones wrote:
> Another reason why having #ifdef's would be useful ...
>
> Rich.
Conditional compilation... I've mulled this over a bit, anyone want to chat
about it?
I've seen using the C pre-processor, but that seems pretty crufty. My approach
has been to conditionally include different source files with just the code that
has to change, but that sometimes makes a weird module layout. Also, OCamlConf
has an untested ability to generate really short "config.ml", but this is pretty
ugly too.
Could MetaOCaml help? (I don't know exactly how much compile-time computation it
can do; never used it)
Any other ideas?
Kenn
-------------------
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:[~2004-04-16 17:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 22:46 [Caml-list] mod_caml Makefile Matt Gushee
2004-04-16 8:11 ` Richard Jones
2004-04-16 16:25 ` Ranjan Bagchi
2004-04-16 16:49 ` Matt Gushee
2004-04-16 16:53 ` Richard Jones
[not found] ` <Pine.LNX.4.58.0404161000290.14222@manjula.frotz.bogus>
2004-04-16 17:12 ` Matt Gushee
2004-04-16 17:17 ` Richard Jones
2004-04-16 17:27 ` Kenneth Knowles [this message]
2004-04-16 18:32 ` [Caml-list] Conditional Compilation (was mod_caml Makefile) skaller
2004-04-16 18:51 ` Kenneth Knowles
2004-04-16 20:37 ` skaller
2004-04-17 0:39 ` Shawn Wagner
2004-04-17 8:46 ` Martin Jambon
2004-04-16 16:49 ` [Caml-list] mod_caml Makefile Richard Jones
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=20040416172726.GC27407@tallman.kefka.frap.net \
--to=kknowles@berkeley.edu \
--cc=caml-list@pauillac.inria.fr \
--cc=rich@annexia.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;
as well as URLs for NNTP newsgroup(s).