From: yoann padioleau <padator@wanadoo.fr>
To: Damien Doligez <damien.doligez@inria.fr>, Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Namespace clash
Date: Thu, 9 Feb 2006 20:32:39 +0100 (CET) [thread overview]
Message-ID: <1372254.1139513559489.JavaMail.www@wwinf1633> (raw)
> > I had not thought about this... Actually, it is not a bad idea, at
> > least, in my build system. Ideally, the build system would have to
> > have a way of mangling the library namespace by packaging up
> > findlib-managed libraries in a single package. Then, it would have
> > to isse the desired -open directives to an ad-hoc camlp4 syntax
> > extension. It's a bit of a hack, but it could work. I wonder if it
> > is general enough a solution to become mainstream, though.
>
> It doesn't have to be a camlp4 extension, you could implement Alain's
> trick
> with a preprocessor written in Bourne shell. But it doesn't work
> when the
> program is already compiled with -pp, since the OCaml compiler doesn't
> allow for a pipeline of preprocessors.
You still can invent a script foo that successfully call your first bourne shell script bar and then
call camlp4.
Then you just pass -pp foo to ocaml.
Did I overlook something ?
>
> -- Damien
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>
next reply other threads:[~2006-02-09 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 19:32 yoann padioleau [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-08 13:28 Alessandro Baretta
2006-02-08 23:41 ` [Caml-list] " Jonathan Roewen
2006-02-09 5:08 ` Alain Frisch
2006-02-09 11:12 ` Alessandro Baretta
2006-02-09 14:52 ` Damien Doligez
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=1372254.1139513559489.JavaMail.www@wwinf1633 \
--to=padator@wanadoo.fr \
--cc=caml-list@inria.fr \
--cc=damien.doligez@inria.fr \
/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).