Disregard for now. Looks like I do need to separate out a wrapper
module, due to my test code "require"-ing the module that has most of
the implementation but also does the "raco" command.
Neil Van Dyke wrote at 06/12/2012 03:35 PM:
If I have a PLaneT package that sets "raco-commands" in "info.rkt",
and when the package is installed from PLaneT via DrRacket, it appears
that the command is run, like the module is fully "require"d.
(I noticed because the command without any arguments does a directory
traversal from current directory, and it appears the current directory
was "/".)
Anyone know offhand whether this is the case, and if so, how to get
around it?
Tell "raco-commands" a small file that's just a wrapper around the
real implementation file, and have the small wrapper file be in
"compile-omit-files"?
Neil V.
____________________
Racket Users list:
http://lists.racket-lang.org/users
