From: Rob Browning <rlb@defaultvalue.org>
Cc: hanwen@cs.uu.nl
Subject: Re: AARRRRGGH! Die Libtool, die!
Date: Tue, 18 Feb 2003 11:14:50 -0600 [thread overview]
Message-ID: <878ywd5x4l.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <200302160056.QAA15802@morrowfield.regexps.com> (Tom Lord's message of "Sat, 15 Feb 2003 16:56:12 -0800 (PST)")
Tom Lord <lord@emf.net> writes:
> Both perl and python are not stable. `sh' hasn't changed much in a
> decade and probably won't for another decade if ever. `sh' is more
> than adequate for the job. If you must reach for something more,
> especially on this list, for gosh sakes, pick something rooted in
> stable standards: reach for SCSH, you traitors.
If SCSH (or even Guile) really is comparable in portability to Perl,
and if we were not concerned with having a large pool of potential
contributors (and we might not be), and if we don't think that the
size of the existing base of systems with the language in question
already installed is relevant, then of course I'd rather use Scheme.
My initial feeling was that at least one of the items above was
probably false, but if not, then that's great.
With respect to sh. I've seen what large "portable sh" programs look
like, and I've worked a bit on them. As a result, I'd have very
little interest in the project if it were written in sh.
Other than that, I agree with much of the rest of what you've said.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-02-18 17:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-15 14:36 AARRRRGGH! Die Libtool, die! Han-Wen Nienhuys
2003-02-15 20:46 ` Rob Browning
2003-02-15 23:54 ` Han-Wen Nienhuys
2003-02-16 0:56 ` Tom Lord
2003-02-18 11:24 ` tomas
2003-02-18 17:14 ` Rob Browning [this message]
2003-02-18 18:50 ` rm
2003-02-19 13:04 ` tomas
2003-02-21 17:28 ` Rob Browning
2003-02-16 1:09 ` Rob Browning
-- strict thread matches above, loose matches on Subject: below --
2003-02-15 14:26 Han-Wen Nienhuys
2003-02-18 11:04 ` tomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878ywd5x4l.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=hanwen@cs.uu.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).