At Thu, 15 May 2014 18:34:20 -0400, Neil Van Dyke wrote:
FYI, a 6.0.1 install from source failed. I can't spend any time on it
right now.
System: 32-bit x86 dual-core, Debian Squeeze, no virtualization, no
swap, 3 GB RAM total, almost 2 GB RAM free.
$ ./configure
Sometimes, `resolved-module-path-name` produces the symbol '|expanded
module|. Is this the only symbol that's produced that _isn't_ the
actual name of a module?
Also, given that I'm calling `expand` on a module form, is it possible
to do something so that I _don't_ end up with '|expanded module|
The result of `expand` does not keep track of it source. You may want
to use `resolve-module-path-index` from `syntax/modresolve`, providing
the original module path as the second argument. The
`resolve-module-path-index` function detects the self module path
index (which is giving you '|expanded
On Fri, May 16, 2014 at 10:23 AM, Matthew Flatt mfl...@cs.utah.edu wrote:
The result of `expand` does not keep track of it source. You may want
to use `resolve-module-path-index` from `syntax/modresolve`, providing
the original module path as the second argument. The
At Fri, 16 May 2014 10:40:44 -0400, Sam Tobin-Hochstadt wrote:
On Fri, May 16, 2014 at 10:23 AM, Matthew Flatt mfl...@cs.utah.edu wrote:
The result of `expand` does not keep track of it source. You may want
to use `resolve-module-path-index` from `syntax/modresolve`, providing
the original
5 matches
Mail list logo
