Bob Burger

I updated the build procedure for Windows so that a virtual machine is no longer required. It uses the Cygwin software on Windows to provide bash, make, etc.

Perhaps the load procedure in c/scheme.c does not handle the library/rt-info and library/ct-info records that run-inner of do-load-binary in s/7.ss does?

Thanks, pull request https://github.com/cisco/ChezScheme/pull/288 fixed this.

It appears to be the macro expander's tracking of source information for the `(display (foo 0))` line that causes the quadratic behavior. If you put the definition alone into a...

I updated the build procedure to use Cygwin. I suspect that MSYS2 may also work, but I haven't tried it. I think the Windows 10 POSIX environment does not allow...

@ovenpasta, thanks for pointing out the makefile's use of the symbolic link ../bin/scheme instead of the file ../bin/$m/scheme. I've fixed that. With regard to using the mingw64 compiler, give it...

Commit e44a209f27f8670c23a1d402b3f968eaa10cad29 adds support for MinGW/MSYS builds of Chez Scheme on Windows. We still use the Microsoft C compiler. The Travis continuous integration server now uses a variant of MSYS_NT...

Can you give an example of what you mean? See https://cisco.github.io/ChezScheme/csug9.5/system.html#./system:s38 for details on Chez Scheme's `eval` function that takes an optional environment argument.

Try adding `(expand '(import (n)))` to hello.ss before calling `eval`. This will load the compile-time information for library (n).

If you do `(eval '(import (n))`, then the variable binding will be available in the interaction environment, and you can use `(eval 'var)`.