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

[Bob Koehler]

In article <7lcsrjF3cki67U1 at mid.individual.net>, billg999 at cs.uofs.edu (Bill Gunshannon) writes:
> 
> 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.

   As VMS Engineering has said, creating a new process with the same
   memory map would be easy, getting around the I/O system differences
   is what would make a UNIX fork() hard in the VMS kernel.

   I suspect there would be little use making VMS do more than it does
   now with the C RTL's current vfork()/exec() emulation, but not doing a
   full UNIX style fork().  Much code that depended on the UNIX kernel's
   behaviour still wouldn't port, and in many cases rewriting to POSIX
   thread calls would get the original functionality in a portable
   manner.  On both UNIX and VMS, multiple threads share the same memory
   map and I/O access.