caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Markus Mottl <markus@mail4.ai.univie.ac.at>
To: Patrick M Doane <patrick@watson.org>
Cc: OCAML <caml-list@inria.fr>
Subject: Re: [Caml-list] canonical camlp4-suffix?
Date: Mon, 3 Sep 2001 18:36:46 +0200	[thread overview]
Message-ID: <20010903183646.B8034@chopin.ai.univie.ac.at> (raw)
In-Reply-To: <Pine.BSF.3.96.1010903120605.42306B-100000@fledge.watson.org>; from patrick@watson.org on Mon, Sep 03, 2001 at 12:06:53 -0400

On Mon, 03 Sep 2001, Patrick M Doane wrote:
> I'm curious - are you going to allow each file to be compiled with
> its own set of camlp4 preprocessors or will it be one set for the
> whole project?

It is always possible for users to provide specific 'make'-rules for
specific files, e.g. when they want to preprocess their OCaml-files in
funny ways. So I don't think it would be a good idea to make things this
complicated.

The main problem is that files containing quotations or syntax extensions
may themselves require preprocessing (e.g. the latter always need this).
It's impossible for 'make' to figure out how to proceed in the general
case. Therefore, I'll only support "first-order" preprocessing with
additional preprocessing flags as required for syntax extensions.

Furthermore, it would be also quite complicated if I supported
implementations of quotations / syntax extensions that spread over several
modules. This would require dependency analysis again. In such difficult
cases the user would be better advised to compile these extensions in
a separate directory and just pass the resulting library to camlp4 via
a flag variable.

I think this scheme should be good enough for most cases. Most people
won't require much more than a couple of quotation files, but don't want
to fiddle around with command line parameters.

Thus, there will only be one list containing all modules that implement
quotations or syntax extensions. They will be compiled before all other
modules and passed to the preprocessor during compilation of the source
files that use the extensions.

> I've seen .mlp sometimes...

Ok, '.mlp' and '.mlip' would be fine for me, too. Any objections?

Regards,
Markus Mottl

-- 
Markus Mottl                                             markus@oefai.at
Austrian Research Institute
for Artificial Intelligence                  http://www.oefai.at/~markus
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


  parent reply	other threads:[~2001-09-03 17:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-03 15:58 Markus Mottl
2001-09-03 16:31 ` Clement Renard
     [not found] ` <Pine.BSF.3.96.1010903120605.42306B-100000@fledge.watson.org>
2001-09-03 16:36   ` Markus Mottl [this message]
     [not found] ` <FLELJKKJEIKNBDJGMIHKGEFKCAAA.franka@cs.uu.nl>
2001-09-03 20:26   ` Markus Mottl
2001-09-04  6:20 ` Daniel de Rauglaudre
2001-09-04 12:43   ` Markus Mottl
2001-09-04 14:00     ` Daniel de Rauglaudre

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=20010903183646.B8034@chopin.ai.univie.ac.at \
    --to=markus@mail4.ai.univie.ac.at \
    --cc=caml-list@inria.fr \
    --cc=patrick@watson.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).