Scheme Request for Implementation 103
"Library Files"
by Derick Eddington.
Its draft and an archive of the ongoing discussion is available at
http://srfi.schemers.org/srfi-103/
You can join the discussion of the draft by sending an email message
with a "subscribe" subject line to
srfi minus 103 minus req...@srfi.schemers.org
You can contribute a message to the discussion by sending it to
srfi minus 1...@srfi.schemers.org
Regards,
The SRFI Editors
[1] http://srfi.schemers.org/srfi-103/srfi-103.html
[2] http://srfi.schemers.org/srfi-103/mail-archive/msg00077.html
--
: Derick
----------------------------------------------------------------
On Sep 25, 1:24 am, srfi-edit...@srfi.schemers.org wrote:
> This announces the availability for discussion of
>
> Scheme Request for Implementation 103
>
> "Library Files"
>
> by Derick Eddington.
>
> Its draft and an archive of the ongoing discussion is available at
>
> http://srfi.schemers.org/srfi-103/
>
> You can join the discussion of the draft by sending an email message
> with a "subscribe" subject line to
>
> srfi minus 103 minus requ...@srfi.schemers.org
Feedback invited.
[1] http://srfi.schemers.org/srfi-103/srfi-103.html
[2] http://srfi.schemers.org/srfi-103/mail-archive/msg00080.html
--
: Derick
----------------------------------------------------------------
http://srfi.schemers.org/srfi-103/mail-archive/msg00091.html
and respond there.
Thank you,
--
: Derick
----------------------------------------------------------------
- Remove implicit file name support.
- Change character encoding design to encoding of code points.
- A lot of clean-up and simplification of the documents, reference
implementation, and tests.
I think the new version is almost ready to be finalized. There is one
remaining issue which I need more feedback about:
Should the "aux", "con", "nul", "prn", etc. file names which are
disallowed by Windows be encoded somehow, so that files for libraries
with such names are nameable on Windows and are exchangeable between
Windows and unixes without renaming? In the current draft, some
characters are encoded for the same reason because Windows disallows
them, so by the same justification for encoding those characters,
should the Windows-disallowed file names also be encoded (e.g. by
encoding their first character)?
Or is this too ugly and stupid of an issue? Not handling this might
help to enrage people to revolt against Windows when such names are
used and don't work on Windows.
But, if we accept that, should the encoding of characters be flushed
altogether (which might help further increase the rage against
Windows)?
But, not being able to name libraries with the same freedom as with
all other symbols (and that freedom is a big thing I love about
Scheme), and allowing the flaws of Windows to determine libraries'
names, and asking that library-name symbols like 'and-let* be renamed
like 'and-let-star, is not acceptable.
I'm not sure what to do...
Please respond here:
http://srfi.schemers.org/srfi-103/mail-archive/msg00119.html
[1] http://srfi.schemers.org/srfi-103/srfi-103.html
[2] http://srfi.schemers.org/srfi-103/mail-archive/msg00118.html
--
: Derick
----------------------------------------------------------------