From:	Martin Stromberg <Martin DOT Stromberg AT epl DOT ericsson DOT se>
Message-Id:	<200104110805.KAA16820@lws256.lu.erisoft.se>
Subject:	Re: New language for autoconf
To:	djgpp-workers AT delorie DOT com
Date:	Wed, 11 Apr 2001 10:05:52 +0200 (MET DST)
In-Reply-To:	<CAEGKOHJKAAFPKOCLHDIMEFECCAA.tim.van.holder@pandora.be> from "Tim Van Holder" at Apr 10, 2001 08:28:25 PM
X-Mailer:	ELM [version 2.5 PL3]
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> 
> > [...]
> > > So I'd like to know what your thoughts on this are. Is
> > > Perl acceptable, or would Python or Guile be preferred?
> > 
> > AFAIK, of the above only Perl is available as a DJGPP port. And automake
> > already uses Perl, anyway, so at least it wouldn't put an _additional_ 
> > burden on most maintainers. Thus, I'd think Perl is the right choice.
> > 
> I know Perl is the only one currently available for DJGPP, but I have
> both Python and Guile sitting on my HD just waiting to be ported :-)
> Python seems fairly easy, while Guile looks to be a challenge.  So my
> question was as much about personal language preference than anything.

In that case: perl, perl, perl. Not python. Don't know Guile so no
comment on that.

However the amount of ported packages from me is zero, so I guess that
gives my vote zero weight.


Right,

						MartinS

- Raw text -