From: skaller <skaller@users.sourceforge.net>
To: Nicolas Pouillard <nicolas.pouillard@gmail.com>
Cc: "jake.donham" <jake.donham@skydeck.com>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] ocamlbuild: args to tags?
Date: Tue, 25 Sep 2007 00:03:37 +1000 [thread overview]
Message-ID: <1190642617.6025.9.camel@rosella.wigram> (raw)
In-Reply-To: <1190636327-sup-9586@ausone.inria.fr>
On Mon, 2007-09-24 at 14:29 +0200, Nicolas Pouillard wrote:
> Excerpts from jake.donham's message of Tue Sep 18 20:01:56 +0200 2007:
> > Hi,
> >
> > Is there a way to pass arguments to a preprocessor via the _tags file?
>
> Yes, but that's not what you want. Moreover this feature is not really
> encouraged.
Just my 2c .. I think all this stuff is wrong. I think it should be
done like this:
(* My Ocaml File .. *)
(*#Syntax Mycamlp4syn *) (* for compatibility *)
#syntax Mycamlp4syn; (* better *)
In other words, if you're using a language mycamplp4syn, you should
say so IN the file using it .. not on the command line.
Ocamlbuild then
* finds the dependencies
* builds them
* applies them to the files using them
I think it is wrong software engineering the current way.
If you use a module you have to either open it or at least use
its name:
List.map
Just because camlp4 modules are *meta* should not excuse them
from this requirement.
Command line should be used for performance tuning and debugging,
and for mapping abstract resources (like modules and syntaxen)
onto the file system .. but not for specifying semantic requirements.
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
next prev parent reply other threads:[~2007-09-24 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 18:01 Jake Donham
2007-09-24 12:29 ` [Caml-list] " Nicolas Pouillard
2007-09-24 14:03 ` skaller [this message]
2007-09-24 15:23 ` Nicolas Pouillard
2007-09-24 17:38 ` skaller
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=1190642617.6025.9.camel@rosella.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@inria.fr \
--cc=jake.donham@skydeck.com \
--cc=nicolas.pouillard@gmail.com \
/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