[Info-vax] C99 updates to CRTL

[Simon Clubley]

On 2019-07-31, John E. Malmberg <wb8tyw at qsl.net_work> wrote:
>
> The CRTL handles the relative filename "net/if.h" correctly with out any 
> issues regardless of any feature settings that I have tried.
>
> What is happening is that include "net/if.h" is being passed to the CRTL 
> as "/net/if.h" and that is where things go wrong if a "net0:" devices 
> exists on the system.  OpenVMS treats "net:" as "net0:".
>

Ouch. That is bad. :-(

Also, why is that path being passed as an absolute path to the CRTL
instead of as a relative path ?

> When the code that translates the filespec encounters "/xxxx/yyyy" and 
> "xxxx" is not a logical name, it needs to check if "xxxx:" is a file 
> structured device, and if it is not file structured, needs to treat 
> "xxxx:" as a non-existent device, instead of trying to look for files on 
> it and returning the error that files are not found.
>

What happens if you have both a mounted disk dka0: and a directory
[dka0] on your default disk ?

(I have not played with the CRTL Unix to VMS filename mapping at this level).

Simon.

-- 
Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980s technology to a 21st century world