unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: rm@fabula.de
Cc: hanwen@cs.uu.nl
Subject: Re: AARRRRGGH! Die Libtool, die!
Date: Tue, 18 Feb 2003 19:50:30 +0100	[thread overview]
Message-ID: <20030218185030.GB30623@www> (raw)
In-Reply-To: <878ywd5x4l.fsf@raven.i.defaultvalue.org>

On Tue, Feb 18, 2003 at 11:14:50AM -0600, Rob Browning wrote:
> 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.

How about 'gu', a really portable guile kernel that can be used to
bootstrap? It seems that  a lot of the portability problems of 'sh' are 
syntax / feature set problems. Wouldn't it be worth the effort to 
work on a (non-interactive) guile-core shell?

 Ralf Mattes


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2003-02-18 18:50 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
2003-02-18 18:50         ` rm [this message]
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=20030218185030.GB30623@www \
    --to=rm@fabula.de \
    --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).