Derick,
I'm not on the SRFI 103 list. I'm writing here as a member of the Ikarus
community.
The new document recommends the file extension 'r6rs-lib'. It also
recommends 'ikarus-r6rs-lib' for Ikarus libraries.
So the SRFI is trying to support multiple dialects. There might also
someday be R7RS and R8RS. There's already Chibi and Chicken which have
their own library systems. So I guess your SRFI would call for
'chibi-lib' and 'chicken-lib' in those cases.
Let's say I keep my files in '~/scheme'. So '~/scheme/abc.sls' is the
library '(abc)'
Is the idea that one can have multiple implementations of a library, one
for each dialect? I.e. have:
~/scheme/abc.r6rs-lib
~/scheme/abc.r7rs-lib
~/scheme/abc.chibi-lib
so that various Scheme systems can find the appropriate library?
If so, I'd like to mention that I wouldn't organize my libraries this
way (multiple dialects in the same tree). I'd have instead separate
library collections, one for each dialect.
Or is the SRFI trying to allow for Scheme systems which themselves
support multiple dialects? In this case, this isn't something that's
found wide practice. Larceny (ERR5RS and R6RS) and PLT do support this.
As I mentioned, I might code in multiple dialects, but I'm not going to
mix up the libraries under the same tree. My Gauche code stays in one
place, my Chibi code another, etc.
So for me, the long file extensions are not necessary.
Otherwise I like the SRFI and appreciate it.
Ed