Re: [racket-dev] Determining if a resolved module path is a real module name

2014-05-16 Thread Matthew Flatt
At Fri, 16 May 2014 10:40:44 -0400, Sam Tobin-Hochstadt wrote: > On Fri, May 16, 2014 at 10:23 AM, Matthew Flatt 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

Re: [racket-dev] Determining if a resolved module path is a real module name

2014-05-16 Thread Sam Tobin-Hochstadt
On Fri, May 16, 2014 at 10:23 AM, Matthew Flatt 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 > `resolve-module-path-index` function dete

Re: [racket-dev] Determining if a resolved module path is a real module name

2014-05-16 Thread Matthew Flatt
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