On Jun 5, 2005, at 7:07 AM, Hans Oesterholt-Dijkema wrote:
For list-related administrative tasks:
http://list.cs.brown.edu/mailman/listinfo/plt-scheme
L.S.,
There seems to be a bug in the Windows variant of mzscheme:
Welcome to MzScheme version 299.100, Copyright (c) 2004-2005 PLT
Scheme, Inc.
> (dynamic-require
"devel\\mzscheme\\collects\\oodb\\backend-sqli-sqlite.scm" 'sqld-new)
> standard-module-name-resolver: expects argument of type <; given
"devel\\mzscheme\\collects\\oodb\\backend-sqli-sqlite.scm"
doesn't work, where
$ mzscheme
Welcome to MzScheme version 299.100, Copyright (c) 2004-2005 PLT
Scheme, Inc.
> (dynamic-require
"devel/mzscheme/collects/oodb/backend-sqli-sqlite.scm" 'sqld-new)
#<
> (exit)
does.
From section 5.4 of the MzScheme manual:
Times • When a module name
is a string,
Courier0000,0000,8080unix-relative-path-stringTimes,
it is interpreted as a path relative to the source of the containing
module (as determined by
CourierA5A5,2A2A,2A2Acurrent-load-relative-directoryTimes
or
CourierA5A5,2A2A,2A2Acurrent-directoryTimes).
Regardless of the platform running MzScheme, the path is always parsed
as a Unix-format path:
Courier/Times
is the path delimiter (multiple adjacent
Courier/Times
are treated as a single delimiter),
Courier..Times
accesses the parent directory, and
Courier.Times
accesses the current directory. To avoid portability problems, the
path elements are further constrained to contain only alpha-numeric
characters plus
Courier-Times,
Courier_Times,
Courier.Times,
and space, and the path may not be empty or contain a leading or
trailing slash.
If I understand your complaint
correctly, you're expecting module-paths to have a platform-specific
separator character, though in MzScheme they don't. As I understand
it, this platform-insensitivity is key in making it possible to write
cross-platform code.
John