Indeed a shortcoming of WSL.
WSL works kind of OK after the april 2018 update. But calls to specific
native Linux system routines often yield strange results.
Also the output of standard Linux commands in WSL is often plain useless or
very limited.
Maybe this will improve in the near future :)
It made me make the move to a Linux under Virtualbox, which works like a
charm!
Best,
Arie
Op ma 2 jul. 2018 om 23:11 schreef Joh-Tob Schäg :
> I recently got a windows pc and installed the linux simulation layer. I
> choose Ubuntu 18.04.
> During executing test.l i noticed the following things
>
> in @test/src/main.l are the following problems:
>
>>
>> (unless (member *OS '("SunOS" "OpenBSD" "Cygwin" "AIX" "HP-UX" "IRIX64"))
>>(sigio (setq "SigSock" (port T 0 "SigPort"))
>> (setq "SigVal" (udp "SigSock")) )
>>(udp "localhost" "SigPort" '(a b c))
>>(wait 200)
>>(test '(a b c) "SigVal")
>>(close "SigSock") )
>>
> raises an error i can not unatangle
>
>
> *
> OS is "Linux"
>
> error is
>
>> ("SigVal")
>
> [test/src/main.l:20] (a b c) -- 'test' failed
>>
>
>
> @test/src/sym.l
>
>>
>>
>> (when symbols
>>(one Foo)
>>(test 'pico (nsp 'symbols))
>>(test 'myLib (nsp 'Foo))
>>(test '(myLib pico) (symbols 'pico)) )
>>
> error:
>
> !? (nsp 'symbols)
> nsp -- Undefined
>
>>
>> (when symbols
>>(test 1 myLib~Foo)
>>(test NIL (nsp 'myLib~Foo)) )
>>
> error: 1 -- 'test' failed
>
>
>> ### zap ###
>> (test "abc" (str? (zap 'abc)))
>>
> The test is wrong, windows is not to blame. I think
>
>
> --- End Windows for Linux Ubuntu18.04 (using latest tests and version 18 2
> 17 of pil)
>
