search

larcenists / larceny

Larceny Scheme implementation
Other
202 stars 32 forks source link

command-line is broken on Windows 10 #826

Open pogrmman opened 5 years ago

pogrmman commented 5 years ago

I'm using Larceny 1.3 on Windows 10 (64-bit), and I've found that the (command-line) procedure from (scheme process-context) only gives (larceny), no matter what the command line arguments are and no matter whether I'm using ordinary command prompt or powershell. (I'd test it on git bash too, but I can't seem to get Larceny to run properly on it).

Here's a quick demo script:

(import (scheme write)
        (scheme process-context))
(display (command-line))

Whether it is invoked on my system with larceny -r7rs test-args.scm -I "%LIBDIR%" -A "%LIBDIR2%" or larceny -r7rs test-args.scm, the only output is (larceny), which is not what it's supposed to do. Even when I associate .scm files with Larceny and invoke it as follows: test-args.scm one two three, I just get (larceny). It also does the same when invoked directly with larceny.bin.exe.

I don't have Larceny on any of my linux systems to test, but I assume it's not broken there.