From: byron@netapp.com (Byron Rakitzis)
To: Bengt.Kleberg@uab.ericsson.se, byron@netapp.com, woods@weird.com
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: RC => POSIX
Date: Wed, 26 Mar 1997 06:54:26 -0500 [thread overview]
Message-ID: <9703261154.AA02882@netapp.com> (raw)
Hey, you don't have to switch to my last name! I hope my last
message was not taken in the wrong light. I was just trying to
clarify my previous words.
I don't think prototyped code should go. ANSI compilers are
practically ubiquitous, and there are filters for converting code
to the old style. Early on, in 1991 maybe, I seem to remember
someone going through this exercise.
I think it would help to clearly define what the goal is of changing
the style with which rc is now coded. I would like to remain
compatible with whatever machines out there right now happily
compile and run rc, and I would also like to make it possible for
rc to be easily ported to a unix that isn't predefined in config.h.
Would all such new unices support posix? Does gnu autoconf effectively
cover the entire space of unices?
Byron.
next reply other threads:[~1997-03-26 16:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-26 11:54 Byron Rakitzis [this message]
1997-03-26 16:45 ` Greg A. Woods
-- 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 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 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=9703261154.AA02882@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).