From: byron@netapp.com (Byron Rakitzis)
To: Bengt.Kleberg@uab.ericsson.se, woods@weird.com
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: RC => POSIX
Date: Tue, 25 Mar 1997 17:30:43 -0500 [thread overview]
Message-ID: <9703252230.AA13737@netapp.com> (raw)
>Byron has written that it is better to be portable than POSIX. He even
>mentioned ANSI C as a stumbeling block for portablility. To be
>consequent I therefore suggest that ANSI C is dropped (or POSIX adopted :-)
I'm not sure what you are saying here. I think I mentioned that
the fake ansi headers that rc ships are an obstacle to portability.
That doesn't have much to do with ansi C.
I think I would like to clean up the source so that it compiles
with an ANSI compiler, but omit the home-grown system prototypes
and typedefs. Perhaps such home-grown prototypes anticipate
portability problems (e.g., having size_t be signed as on SunOS 4
could imply any number of bugs if the code assumes unsigned), but
I am not sure.
next reply other threads:[~1997-03-25 22:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-25 22:30 Byron Rakitzis [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-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 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=9703252230.AA13737@netapp.com \
--to=byron@netapp.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).