| Date: Sat, 13 Aug 2011 12:17:54 -0400
 | From: John Cowan <cowan@mercury.ccil.org>
 |
 | Andy Wingo scripsit:
 |
 | > Include is valuable, no doubt about it.  However `load' with
 | > relative paths does not make any portable kind of sense.  If you
 | > want to load code at runtime portably, build an absolute path.
 |
 | Absolute paths are less portable than relative ones -- why, Windows
 | and Posix don't even agree on what an absolute path looks like, not
 | to mention that different systems are laid out differently.
 | Relative paths with slashes (which the Windows kernel is fine with,
 | though various parts of the UI insist on backslashes) are the
 | nearest thing to portability we have.

The operative word here is "build".  In SLIB, a Scheme program builds
catalog paths (absolute or relative) on the host when it is installed.
While those paths are radically different on different
operating-systems, they don't change on a host.

_______________________________________________
Scheme-reports mailing list
Scheme-reports@scheme-reports.org
http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports