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

[Arne Vajhøj]

VAXman- @SendSpamHere.ORG wrote:
> In article <4ae79c4e$0$282$14726298 at news.sunsite.dk>, =?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne at vajhoej.dk> writes:
>> Richard B. Gilbert wrote:
>>> JF Mezei wrote:
>>>> Richard B. Gilbert wrote:
>>>>> We have managed to get along without fork() for about thirty
>>>>> years.
>>> I've programmed for for VMS VAX and Alpha for about thirty-five years 
>>> without missing fork() in the slightest.  YMMV
>>>
>>> Of course I started my career ca. 1966 with SDS 900 series machines 
>>> which ran a long forgotten O/S and used a long forgotten command 
>>> language. Unix was still imprisoned at Bell Laboratories and Berkeley. 
>>>  From that I moved to IBM mainframe.  None of these systems offered or 
>>> needed fork() or vfork().
>> AFAIK there are no programming task that requires fork.
>>
>> But porting code using fork to a system with no fork is
>> often a lot of work.
> 
> But porting code using ASTs to a system with no ASTs is
> often a lot of work.

Yes. But that does not seem to be problem in this case.

> The issue here is is anyone porting or are they just trying
> to make the unixy code compile and run as is?  
> 
> |"Porting" is the act of migrating some or all of the desired 
> |functionality of a product from one computer system to another.
> |[...]since even a well-done port will not transfer 100% of the
> |product being ported, and some changes will have to be made.
> --source: a fool.

If you consider build scripts a part of the entire software, then
it is the same thing.

Arne