caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Kenneth Oksanen <cessu@hutcs.cs.hut.fi>
To: la@iki.fi
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] autoconf and caml
Date: Fri, 06 Sep 2002 13:12:31 +0300	[thread overview]
Message-ID: <E17nG6J-0005Bs-00@hutcs.cs.hut.fi> (raw)
In-Reply-To: <20020905161617.A29272@kruuna.Helsinki.FI> (message from Lauri Alanko on Thu, 5 Sep 2002 16:16:18 +0300)

>On Thu, Sep 05, 2002 at 03:23:17PM +0300, Kenneth Oksanen wrote:
>> ocamllex produces code that is not cpp-safe.
>Can't you use m4 or some other (marginally) less brain-dead preprocessor?

I could use m4 or camlp4 or whatever, if GNU autoconf and assorted
auto* -tools would produce them.

People seem to have missed the actual problem I have posed: what is
the most convenient and hassle-free mechanism for transporting
information produced by running ./configure to O'Caml source code?
Such features include directory prefixes, auxiliary program paths,
various constants, features {en,dis}abled with --enable-X and alike.
I'm *NOT* trying to use the preprocessor for any weird syntactic
abstractions or anything of that kind.

>From the answers I've seen so far, no common, truly convenient and
completely hassle-free mechanism exists.  Hopefully this problem will
find a clean solution some day.  In the meantime I can live with -pp cpp
and bite a few small kludges, like adding a (*don't remove me*) ;-)

-=-
; Kenneth Oksanen, email: cessu@iki.fi, http://www.iki.fi/~cessu
((lambda(a) (a a((lambda(a)(lambda()(set! a(+ a 1))a))1)))(lambda(a c)
((lambda(b) (newline)(write b)(a a((lambda(c)(lambda()(c c)))(lambda(a)
((lambda(c) (if(=(modulo c b)0)(a a)c))(c))))))(c)))) ; Scheme me!
-------------------
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


  reply	other threads:[~2002-09-06 10:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-04 15:20 Kenneth Oksanen
2002-09-05 11:57 ` Xavier Leroy
2002-09-05 12:23   ` Kenneth Oksanen
2002-09-05 12:53     ` Olivier Andrieu
2002-09-05 13:16     ` Lauri Alanko
2002-09-06 10:12       ` Kenneth Oksanen [this message]
2002-09-06 10:25         ` Jun P.FURUSE
2002-09-06 10:46         ` Yann Régis-Gianas
2002-09-06 10:56           ` Yaron M. Minsky
2002-09-06 11:07             ` Maxence Guesdon
2002-09-06 12:31               ` pa_ifdef [Was: Re: [Caml-list] autoconf and caml] Stefano Zacchiroli
2002-09-06 12:52                 ` Daniel de Rauglaudre
2002-09-08 10:07                   ` Stefano Zacchiroli
2002-09-09  8:59                     ` Daniel de Rauglaudre
2002-09-06 11:33             ` [Caml-list] autoconf and caml Yann Régis-Gianas
2002-09-06 11:22               ` Yaron M. Minsky
2002-09-06 11:28                 ` Jérôme Marant
2002-09-06 11:41                   ` Yaron M. Minsky
2002-09-06  9:42   ` Hendrik Tews

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=E17nG6J-0005Bs-00@hutcs.cs.hut.fi \
    --to=cessu@hutcs.cs.hut.fi \
    --cc=caml-list@inria.fr \
    --cc=la@iki.fi \
    /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).