l...@gnu.org (Ludovic Courtès) writes: > Hi, > > Mark H Weaver <m...@netris.org> skribis: > >> Any objections to adding ".guile.sls" and ".sls" to Guile's default >> %load-extensions? > > OK for .sls, but why .guile.sls? > This is used for compatibility libraries, for instance:
% ls spells/filesys/ compat.guile.sls compat.larceny.sls compat.mzscheme.sls compat.ikarus.sls compat.mosh.sls compat.ypsilon.sls Only guile will have .guile.sls in its %load-extensions, so it will find the correct library, in this case corresponding to the library name `(spells filesys compat)'. Other R6RS implementations, if the adhere to this convention, will only consider "their" specific file, as they'd only look for spells/filesys/compat.sls and spells/filesys/compat.<IMPLEMENTATION>.sls. If there's a portable implementation of that library, it will be under spells/filesys/compat.sls, and be used (only) if there's no implementation-specific file. So it's important that the ".guile.sls" extension is considered *before* ".sls". For performance reasons, it *might* make sense to not enable this behavior by default, but provide a command-line switch; however, enabling this behavior is *already* possible using command-line switches ("-x .guile.sls -x .sls"), so I don't know... Regards, Rotty -- Andreas Rottmann -- <http://rotty.yi.org/>