Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
[Caml-list] autoconf and caml
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Kenneth Oksanen <cessu@h...>
Subject: Re: [Caml-list] autoconf and caml
>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:,
((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 Archives:
Bug reports: FAQ:
Beginner's list: