Re: Perl vs Scheme vs ML vs ... for autoconf

2001-04-26 Thread Gary V . Vaughan
On Monday 23 April 2001 4:29 pm, Akim Demaille wrote: > > "Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes: > > Alexandre> That's why we should have this portability library coded in > Alexandre> m4sh. Instead of repeatedly fixing the same problems over > Alexandre> and over, we should ha

Re: Perl vs Scheme vs ML vs ... for autoconf

2001-04-23 Thread Akim Demaille
> "Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes: Alexandre> That's why we should have this portability library coded in Alexandre> m4sh. Instead of repeatedly fixing the same problems over Alexandre> and over, we should have them coded right once, and then Alexandre> used all over. Th

Re: Perl vs Scheme vs ML vs ... for autoconf

2001-04-20 Thread Gary V . Vaughan
On Thursday 12 April 2001 11:17 am, Akim Demaille wrote: > > "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes: > > Alexandre> On Apr 11, 2001, Akim Demaille <[EMAIL PROTECTED]> wrote: > >> We are about to write new tools, typically autom4te, on top of > >> which autoheader, autoconf e

Re: Perl vs Scheme vs ML vs ... for autoconf

2001-04-12 Thread Akim Demaille
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes: Alexandre> On Apr 11, 2001, Akim Demaille <[EMAIL PROTECTED]> wrote: >> We are about to write new tools, typically autom4te, on top of >> which autoheader, autoconf etc. will be rewritten. I'm fed up with >> addressing portability

Re: Perl vs Scheme vs ML vs ... for autoconf

2001-04-11 Thread Alexandre Oliva
On Apr 11, 2001, Akim Demaille <[EMAIL PROTECTED]> wrote: > We are about to write new tools, typically autom4te, on top of which > autoheader, autoconf etc. will be rewritten. I'm fed up with > addressing portability issues on the maintainer side. That's why we should have this portability libr

Re: Perl vs Scheme vs ML vs ... for autoconf

2001-04-11 Thread Akim Demaille
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes: >> But again, Autoconf is addressing portability issues on the user >> side, not on the maintainer side. Alexandre> Why not address them on the maintainer side too? Why not Alexandre> have our own dog food? :-) Alexandre> AC_PLAI

Re: Perl vs Scheme vs ML vs ... for autoconf

2001-04-10 Thread Alexandre Oliva
On Apr 10, 2001, Akim Demaille <[EMAIL PROTECTED]> wrote: >> "Russ" == Russ Allbery <[EMAIL PROTECTED]> writes: Russ> Is there any way that the driver scripts could be generated Russ> using M4 so that all the portability junk can be hidden, just Russ> like autoconf lets the end user do for th

Re: Perl vs Scheme vs ML vs ... for autoconf

2001-04-10 Thread Guido Draheim
a) automake was not ported from perl to guile for years, and I don't know of experiments to actually do it now, or have it done in this decade (it wasn't in the last). Moving it from perl to guile does not earn much for features or maintainability - it would just be another point

Re: Perl vs Scheme vs ML vs ... for autoconf

2001-04-10 Thread Akim Demaille
> "Russ" == Russ Allbery <[EMAIL PROTECTED]> writes: Russ> Is there any way that the driver scripts could be generated Russ> using M4 so that all the portability junk can be hidden, just Russ> like autoconf lets the end user do for the configure script? That's correct, and that's what Autom4

Re: Perl vs Scheme vs ML vs ... for autoconf

2001-04-10 Thread Russ Allbery
Akim Demaille <[EMAIL PROTECTED]> writes: > I have been frightened by the number of problems we had with the > different AWKs and seds. I'm tired of the need to rewrite everything n > times, n being the number of .sh in Autoconf. Tim is fighting n times > with portability issues for DJGPP for t

Re: Perl vs Scheme vs ML vs ... for autoconf

2001-04-10 Thread Akim Demaille
> "Paul" == Paul Eggert <[EMAIL PROTECTED]> writes: >> All I'm looking for is a decent language for the driver, i.e., >> rewrite autoconf.sh into something better than sh. Paul> For that application, I'm not entirely convinced that it's worth Paul> the hassle to switch. But it's not a big d

Re: Perl vs Scheme vs ML vs ... for autoconf

2001-04-10 Thread Paul Eggert
> Cc: [EMAIL PROTECTED] > From: Akim Demaille <[EMAIL PROTECTED]> > Date: 10 Apr 2001 19:03:14 +0200 > User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) > > > "Paul" == Paul Eggert <[EMAIL PROTECTED]> writes: > > Paul> Scheme by far is the best choice for this kind of appli

Re: Perl vs Scheme vs ML vs ... for autoconf

2001-04-10 Thread Russ Allbery
Paul Eggert <[EMAIL PROTECTED]> writes: > Certainly Perl could be used, but for this application it would almost > certainly be less readable and maintainable than Scheme would be, > assuming similar competence levels for Perl and for Scheme. I adore Perl and use it constantly for all sorts of t

Re: Perl vs Scheme vs ML vs ... for autoconf

2001-04-10 Thread Akim Demaille
> "Paul" == Paul Eggert <[EMAIL PROTECTED]> writes: Paul> Scheme by far is the best choice for this kind of application, Paul> because it's best at programs that generate other programs. The Paul> other languages mentioned are not even close. I might be wrong, but I think there is some conf

Re: Perl vs Scheme vs ML vs ... for autoconf

2001-04-10 Thread Paul Eggert
> From: Alexandre Oliva <[EMAIL PROTECTED]> > Date: 10 Apr 2001 08:49:15 -0300 > > I hate Perl. Really. I mean it. I wouldn't go that far. But perhaps I'm biased: * I worked down the hall from Larry Wall when he invented Perl. * In 1993 Stott Parker and I published one of the first acade