rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Bengt.Kleberg@ms.uab.ericsson.se (Bengt Kleberg)
To: rc@hawkwind.utcs.toronto.edu, culliton@clark.net
Subject: Re: RC => POSIX
Date: Thu, 6 Mar 1997 09:09:45 -0500	[thread overview]
Message-ID: <199703061409.PAA27178@uabx01c184.uab.ericsson.se> (raw)


> From rc-owner@hawkwind.utcs.toronto.edu Thu Mar  6 14:48:52 1997
> From: Tom Culliton <culliton@clark.net>
> Date: 	Thu, 6 Mar 1997 08:46:06 -0500
> To: Bengt.Kleberg@ms.uab.ericsson.se, rc@hawkwind.utcs.toronto.edu
> Subject: Re: 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.
> >
...deleted explanation why this wouldn't be a good idea
> >

OK, I just like the idea, have tried it successfully (with far fewer
target systems) and hoped it would be doable.

> All your proposal
> would do is move the #if's into the compatibility library.

Actually I meant to use a specific library for each operating system,
so there would be several libraries with no #ifdef's in any of them.
This is probably just a case of personal taste. I prefer several
libraries, others prefer serveral #ifdef's.

Best Wishes, Bengt
--------------------------------------------------------------------
Email: Bengt.Kleberg@enea.se (Enea Data AB, Sweden)
Disclaimer: Nothing abovementioned has any connection to Enea Data AB
``At the moment money does indeed make the world go round but unfortunately
  the direction of that applied rotation is all downhill.'' fleecy@netreach.net


             reply	other threads:[~1997-03-06 14:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-03-06 14:09 Bengt Kleberg [this message]
  -- 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
1997-03-06 17:15 Alan Watson
1997-03-06 17:54 ` Scott Schwartz
     [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 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=199703061409.PAA27178@uabx01c184.uab.ericsson.se \
    --to=bengt.kleberg@ms.uab.ericsson.se \
    --cc=culliton@clark.net \
    --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).