Date: Thu, 12 Apr 2001 12:50:52 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
cc: djgpp-workers AT delorie DOT com
Subject: Re: New language for autoconf
In-Reply-To: <CAEGKOHJKAAFPKOCLHDIMEFECCAA.tim.van.holder@pandora.be>
Message-ID: <Pine.SUN.3.91.1010412125022.15826H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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
Precedence: bulk


On Tue, 10 Apr 2001, Tim Van Holder wrote:

> > 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.