From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from weaver-gw.netapp.com ([198.95.224.2]) by hawkwind.utcs.utoronto.ca with SMTP id <24642>; Tue, 25 Mar 1997 17:30:16 -0500
Received: from netapp.com ([192.9.200.1]) by weaver.netapp.com with SMTP id <15948-1940>; Tue, 25 Mar 1997 14:29:18 -0000
Received: by netapp.com (4.1/SMI-4.1)
	id AA13737; Tue, 25 Mar 97 14:30:43 PST
Date:	Tue, 25 Mar 1997 17:30:43 -0500
From:	byron@netapp.com (Byron Rakitzis)
Message-Id: <9703252230.AA13737@netapp.com>
To:	Bengt.Kleberg@uab.ericsson.se, woods@weird.com
Subject: Re: RC => POSIX
Cc:	rc@hawkwind.utcs.toronto.edu

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