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

[Bill Gunshannon]

In article <WELl3PK2e4nk at eisner.encompasserve.org>,
	koehler at eisner.nospam.encompasserve.org (Bob Koehler) writes:
> In article <7ktlhfF3af5v3U13 at mid.individual.net>, Bob Eager <rde42 at spamcop.net> writes:
>> 
>> Exactly. It 'costs' quite a bit more. Fair enough, but it means that a 
>> proper port ought to consider those issues and not just do them 'the UNIX 
>> way'.
> 
>    Yes, processes on VMS are heavier, and process creation costs more.
>    Which is why in porting fork() stuff from UNIX I generally prefer
>    to replace multiple forks with multiple POSIX threads.  Only
>    create a process if you need a new executable in it.

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.

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>