Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!nike!sri-spam!sri-unix!hplabs!tektronix!uw-beaver!tikal!sigma!bill
From: bill@sigma.UUCP (William Swan)
Newsgroups: net.micro.cpm
Subject: standardizing BDS C (sort of)
Message-ID: <882@sigma.UUCP>
Date: Tue, 7-Oct-86 17:59:36 EDT
Article-I.D.: sigma.882
Posted: Tue Oct  7 17:59:36 1986
Date-Received: Wed, 8-Oct-86 19:31:51 EDT
Reply-To: bill@sigma.UUCP (William Swan)
Lines: 27
Keywords: BDS C, standards

References:


[]
Has anybody "standardized" BDS C?


I have been working (playing) with a BDS C compiler lately, and have 
been subjected to a number of annoyances related to its non-standard
I/O routines which carry standard names, such as fopen().

A few years back somebody wrote a set of routines, sfopen() et al, 
that work like the "real" thing. I expanded and incorporated those into
"my" libraries, but there is still the problem of finding and changing
names in p/d programs to be compiled with BDS C.

I would like to reorganize the standard libraries so that the "new"
standard functions would work just like the "real" thing. A quick
survey shows the following routines (there may be others) to be
(possibly) nonstandard in some potentially critical way:

	puts()	getline()?
	open()	creat()	read()	write()	seek()?	tell()?
	fopen()	fgets()?

If anybody has done this before (or knows of it being done), I would
appreciate sources, pointers, or hints.

---
Bill Swan	{decvax,allegra,ihnp4}!uw-beaver!tikal!sigma!bill