rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Alan Watson <alan@oldp.nmsu.edu>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: RC => POSIX
Date: Thu, 6 Mar 1997 12:15:49 -0500	[thread overview]
Message-ID: <9703061715.AA30380@oldp.nmsu.edu> (raw)

> >Agreed, "all the old BSD and SysV systems" would fall behind. 
> [...]
> 
> [...]
> There's a lot of old iron out there doing useful work.  Ask Byron, I'm
> sure he had a lot of mail from folks with strange incompatibilities.

Lets stop and look at where we are.

The behaviour of rc is, for all intents and purposes, fixed. We are
talking about rc-1.5 not because we want new features or want bugs
fixed, but because we want rc-1.4 to work on new iron. Presumably,
those people with old iron can continue to run rc-1.4.

Making rc-1.5 run on just POSIX systems would make it significantly
easier to maintain. Given the resources that are available, this is a
very worthy goal.

(On a related note, separating rc from readline would make it
significantly easier to maintain, but lets not get into that one
again.)

Alan


             reply	other threads:[~1997-03-06 17:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-03-06 17:15 Alan Watson [this message]
1997-03-06 17:54 ` Scott Schwartz
  -- strict thread matches above, loose matches on Subject: below --
1997-03-29 20:23 Bengt Kleberg
1997-03-27  9:58 Malte Uhl
1997-03-26 11:54 Byron Rakitzis
1997-03-26 16:45 ` Greg A. Woods
1997-03-26  8:33 Bengt Kleberg
1997-03-26 16:38 ` Greg A. Woods
1997-03-25 22:30 Byron Rakitzis
1997-03-24  9:18 Bengt Kleberg
1997-03-24 20:22 ` Greg A. Woods
1997-03-08  0:13 Byron Rakitzis
1997-03-06 17:40 Tom Culliton
     [not found] <199703061512.KAA21040@explorer2.clark.net>
1997-03-06 16:57 ` Malte Uhl
1997-03-06 16:54 Tom Culliton
1997-03-06 15:22 Tom Culliton
1997-03-06 14:09 Bengt Kleberg
1997-03-06 13:46 Tom Culliton
1997-03-06 10:16 Bengt Kleberg
1997-03-07  1:45 ` Greg A. Woods

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9703061715.AA30380@oldp.nmsu.edu \
    --to=alan@oldp.nmsu.edu \
    --cc=rc@hawkwind.utcs.toronto.edu \
    /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 NNTP newsgroup(s).