[Info-vax] Looking into C-include files on VMS

[Bill Gunshannon]

In article <hcrfk0$bth$3 at naig.caltech.edu>,
	glen herrmannsfeldt <gah at ugcs.caltech.edu> writes:
> Bill Gunshannon <billg999 at cs.uofs.edu> wrote:
> (snip)
>  
>> fork() is more than just creating a news process.  It is not just
>> the overhead that make sit a show stopper on VMS.  It is also things
>> like sharing all the variable and open files/devices.  Unless things
>> have changed considerably since the last time I tried it VMS just
>> flat out can't do that.
> 
> I do think this is one place where Unix goofed.  It is an interesting
> model, but in practice it is strange.  As it is rare that you want
> to share the variables and open files, and most common to exec(),
> vfork() was added.  

If that were the case then VMS's lack of a true fork() would not be
a problem.  But a lot of Open Source (and old Unix software before
the Open Source world tried to claim they invented free software)
does, in fact, utilize these features.

> 
> I presume VMS has some way to share data when needed, though.
 
None that I have ever seen.

bill

-- 
Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolves
billg999 at cs.scranton.edu |  and a sheep voting on what's for dinner.
University of Scranton   |
Scranton, Pennsylvania   |         #include <std.disclaimer.h>