>>>>> "Paul" == Paul Berrevoets <[EMAIL PROTECTED]> writes:
>> If you want to get folks using and improving Java macros, you need
>> to make them part of the "standard" install.
Paul> I concur that Java is ubiquitous enough to warrant "standard"
Paul> support.
The long range goal is to have Autoconf support *any* language via the
usual m4/*.m4 files. Today, with 2.13, this is impossible: you no
longer can use the regular interface of AC_CHECK_FUNC etc.
Today, with CVS Autoconf *much* of it possible. No doubt there remain
things to clarify and check, this is why it would be wonderful if Mo
could try to integrate Java support *before 2.50*: because it is a
good torture test for the interlinguaization (ouch!) of Autoconf. It
would be a pain if the interface offered by 2.50 was limited as it
would mean we'd have to keep that crap in 2.51 etc.
I stress that it should be as easy to implement support for a user as
for the Autoconf maintainers. You don't (shouldn't?) need to change
any internal, just add new things.
Akim
