Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!info-vax
From: H_Eidnes%vax.runit.unit.uninett@NTA-VAX.ARPA (H}vard Eidnes)
Newsgroups: mod.computers.vax
Subject: Re: Vax C V2.0 open bug
Message-ID: <628:H_Eidnes@vax.runit.unit.uninett>
Date: Sat, 16-Nov-85 03:28:25 EST
Article-I.D.: vax.628:H_Eidnes
Posted: Sat Nov 16 03:28:25 1985
Date-Received: Sat, 16-Nov-85 20:55:56 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 12
Approved: info-vax@sri-kl.arpa

> Any program that relies on getting a particular file descriptor at a
> particular point in its execution is broken.  ...

Well, the fact remains that the semantics that you get the
*lowest free* file descriptor is *documented* in every Unix
Programming Manual (at least all that I have come across...),
so all programmers creating programs to be run under Unix, 
can rely on this "feature". So if Vax/Vms C should be "compatible" 
with Unix C, it should also implement and document this feature.

If it is a wise design decision to impose this rule in the first
place, however, is another matter...