rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: woods@most.weird.com (Greg A. Woods)
To: Bengt.Kleberg@ms.uab.ericsson.se (Bengt Kleberg)
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: RC => POSIX
Date: Thu, 6 Mar 1997 20:45:47 -0500	[thread overview]
Message-ID: <m0w2ojD-00076wC@most.weird.com> (raw)
In-Reply-To: Bengt Kleberg's message of "Thu, March 6, 1997 05:16:15 -0500" regarding "RC => POSIX" id <199703061016.LAA26568@uabx01c184.uab.ericsson.se>

[ On Thu, March 6, 1997 at 05:16:15 (-0500), Bengt Kleberg wrote: ]
> Subject: RC => POSIX
> What if we wrote rc to posix (or UNIX(tm) if posix isn't enough) and
> removed as much of the #ifdef's as possible. Then, on systems without
> posix support, we could  create a posix library for that operating
> system. Only covering the missing posix calls that rc uses, ofcourse.

It would be far more productive and result in a far more portable
product to integrate GNU Autoconf et al and didn't I just see a note
about es being autoconf'ed pass by here earlier?  Taking the autoconf
support from es should be trivial, esp. to any rc-internals programmer
with any experience using autoconf.

The GNU Autoconf philosophy is similar in some ways to what you suggest,
esp. in that autoconf'ed packages usually provide a compatability
library for those system functions the software uses but which are not
always available on all systems.  However the autoconf style isn't
anywhere nearly so restrictive as porting directly to plain POSIX would

(BTW, w.r.t. the GNU readline signal problems, my adivce is don't use
GNU readline -- it isn't very good at what it does, is far too big, and
is very difficult to integrate into a program that tries to do job
control.  There were other command-line editing libraries for rc long
ago, and there are other new ones too that might be tried.  I've had
good luck with the command-line editing support in pdksh and it seems to
integrate well with a shell, and it supports both vi and emacs modes.)

							Greg A. Woods

+1 416 443-1734			VE3TCP			robohack!woods
Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com>

  reply	other threads:[~1997-03-07  1:45 UTC|newest]

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

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:

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

  git send-email \
    --in-reply-to=m0w2ojD-00076wC@most.weird.com \
    --to=woods@most.weird.com \
    --cc=Bengt.Kleberg@ms.uab.ericsson.se \
    --cc=rc@hawkwind.utcs.toronto.edu \
    --cc=woods@weird.com \


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