fopen(), etc. in X3J11 Draft Standard

[Chris Miller]

I notice that the February 1986 X3J11 draft standard for C omits
mention of fopen(), freopen() and fclose() (except in the index, which
is full of errors and appears to refer to an earlier draft).

Am I right to assume that this omission is deliberate?  I can see that
some systems may be unable to provide the facility of opening a file
whose name is supplied from within a program, but would have thought
that in practice such systems are now very rare.  In any case, there
should surely be a form of words that allows the standard to say "this
facility need not be available, but if it is, it should look like
this"; in effect, this has been done with kill/signal.

Or is the omission simply a slip of the word-processor?
-- 
	Chris Miller, Heriot-Watt University, Edinburgh
	...!ukc!hwcs!chris   chris at hwcs.uucp	chris at cs.hw.ac.uk