From: woods@most.weird.com (Greg A. Woods)
To: Bengt.Kleberg@uab.ericsson.se (Bengt Kleberg)
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: RC => POSIX
Date: Mon, 24 Mar 1997 15:22:12 -0500 [thread overview]
Message-ID: <m0w9GFw-00076vC@most.weird.com> (raw)
In-Reply-To: Bengt Kleberg's message of "Mon, March 24, 1997 10:18:15 +0100" regarding "Re: RC => POSIX" id <199703240918.KAA15116@uabx04c397.uab.ericsson.se>
[ On Mon, March 24, 1997 at 10:18:15 (+0100), Bengt Kleberg wrote: ]
> Subject: Re: RC => POSIX
>
> This is what I don't like. When it comes to programming I prefer restrictions.
Perhaps you're not aware of just how restrictive POSIX programming must
be. Where it's not restricted things are left completely un-defined.
At least with the general GNU coding all variants of systems can be
taken into account and all features of systems can be used.
--
Greg A. Woods
+1 416 443-1734 VE3TCP robohack!woods
Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com>
next prev parent reply other threads:[~1997-03-24 21:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-24 9:18 Bengt Kleberg
1997-03-24 20:22 ` Greg A. Woods [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-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 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=m0w9GFw-00076vC@most.weird.com \
--to=woods@most.weird.com \
--cc=Bengt.Kleberg@uab.ericsson.se \
--cc=rc@hawkwind.utcs.toronto.edu \
--cc=woods@weird.com \
/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).