Hi Ralph,
On Mon, 15 Apr 2013 18:29:16 +0200, Marc Feeley <feeley@iro.umontreal.ca>
wrote:
...
>> This brings me to Gambit, via Black Hole. BH contains some code (in...
>> compile-load.scm and lib.scm) that assumes `/dev/null' exists. This is
>> obviously not true on Windows where instead we have `NUL'. It's easy
>> enough to modify BH accordingly but the problem remains that Gambit
>> tries to normalize all paths passed to `compile-file-to-target' so we
>> end up with `<absolute path to cwd>\NUL' instead of just `NUL'. This
>> essentially prevents us from using the null device as input to
>> `compile-file-to-target' on Windows
> There was an issue with opening UNC filenames (Universal NamingAwesome, thanks a lot for fixing this. Being able to access the null device
> Convention) on Windows that I have now fixed. So now it is possible to
> use \\.\nul for the nul device (so "/dev/null" should be replaced with
> "\\\\.\\nul" on Windows). Note that the path-expansion algorithm will
> map "nul" to "<cwd>/nul" so a (open-output-file "nul") will open a local
> file called "nul". This consistency with Unix is a good thing.
on Windows means I can now try to get Black Hole trunk working on Windows.
_______________________________________________
Gambit-list mailing list
Gambit-list@iro.umontreal.ca
https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list