caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Dario Teixeira <darioteixeira@yahoo.com>
Cc: blue storm <bluestorm.dylc@gmail.com>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] OSR: META files for packages containing syntax extensions
Date: Fri, 14 Mar 2008 16:51:26 +0100	[thread overview]
Message-ID: <1205509886.22905.4.camel@flake.lan.gerd-stolpmann.de> (raw)
In-Reply-To: <983301.78248.qm@web54604.mail.re2.yahoo.com>


Am Freitag, den 14.03.2008, 15:33 +0000 schrieb Dario Teixeira:
> > Is there a way to specify a dependency on a specific preprocessor
> > (between camlp4o and camlp4r, for example ?). Most extension actually
> > won't work with both syntaxes (classical and revised), and it could be
> > helpful to make it apparent in the package description (although most
> > of the time an horrible preprocessor-runtime error will happen).
> > More generally, i'm concerned with the possible incompatibilities
> > between syntax extensions (however, this may be a bit off-topic).
> 
> I don't know if there's support for those cases (are there any in the wild?).
> Perhaps some of Findlib's gurus can enlighten us...

Currently this is not possible. We could do something like

error(camlp4r) = "This extension is not compatible with revised syntax"

if there is really a demand for it.

Gerd

> 
> Cheers,
> Dario
> 
> 
> 
>       ___________________________________________________________ 
> Rise to the challenge for Sport Relief with Yahoo! For Good  
> 
> http://uk.promotions.yahoo.com/forgood/
> 
> _______________________________________________
> 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
> 
-- 
------------------------------------------------------------
Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany 
gerd@gerd-stolpmann.de          http://www.gerd-stolpmann.de
Phone: +49-6151-153855                  Fax: +49-6151-997714
------------------------------------------------------------



  reply	other threads:[~2008-03-14 15:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13 12:40 Dario Teixeira
2008-03-13 13:14 ` Sylvain Le Gall
2008-03-13 13:21   ` Eric Cooper
2008-03-13 13:30     ` Sylvain Le Gall
2008-03-14 15:00       ` [Caml-list] " Dario Teixeira
2008-03-14 14:53     ` Dario Teixeira
2008-03-14 14:52   ` Dario Teixeira
2008-03-14 15:09     ` Sylvain Le Gall
2008-03-14 15:41       ` [Caml-list] " Dario Teixeira
2008-03-13 15:05 ` [Caml-list] " Stefano Zacchiroli
2008-03-13 15:30   ` Gerd Stolpmann
2008-03-13 17:08     ` blue storm
2008-03-14 15:33       ` Dario Teixeira
2008-03-14 15:51         ` Gerd Stolpmann [this message]
2008-03-16 21:34 ` [Caml-list] OSR: META files for packages containing syntax extensions (take 2) Dario Teixeira

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=1205509886.22905.4.camel@flake.lan.gerd-stolpmann.de \
    --to=info@gerd-stolpmann.de \
    --cc=bluestorm.dylc@gmail.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=darioteixeira@yahoo.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;
as well as URLs for NNTP newsgroup(s).