Mo DeJong wrote:
> The thing I have noticed about open source projects is that the
> only way to get things done is to decide on a goal and then do
> 99% of the work needed to reach that goal. Other folks are happy to
> make comments on the work you did or polish up the 1% you did wrong,
> but nobody is going to do the work for you. My goal is to get Java
> support into autoconf so that I do not need to maintain my own
> set of compiler macros. If folks can agree that Java support in
> autoconf is a good thing, then I will do most of the work needed to
> make that happen. I am not going to waste lots of time hacking
> autoconf if people are not interested in adding Java support. It is
> also a waste of my time to put these macros on the macro archive.
> The macro archive is not the place for language support in autoconf!
I would like to add my voice of encouragement and express that I would very much
like to see improved Java support in the auto* tools.
> If you want to get folks using and improving Java macros, you need to
> make them part of the "standard" install.
I concur that Java is ubiquitous enough to warrant "standard" support.
--
Regards,
Paul
