From:	"Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To:	<djgpp-workers AT delorie DOT com>
Subject:	RE: New language for autoconf
Date:	Thu, 12 Apr 2001 18:34:18 +0200
Message-ID:	<CAEGKOHJKAAFPKOCLHDIIEHCCCAA.tim.van.holder@pandora.be>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To:	<Pine.SUN.3.91.1010412125022.15826H-100000@is>
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
Importance:	Normal
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

> > > 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 :-)
> 
> I tend to recommend Perl.  Its port is used for quite some time and
> was proven to be stable and reliable.  New ports are always less
> stable.

Mostly a moot question now anyway; since Akim is the one going to do
the implementing, he decided on Perl.  It was also the general consensus
that using perl was the least burden for maintainers, as perl is fairly
ubiquitous.

- Raw text -