Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

SRFI 103: Library Files

1 view
Skip to first unread message

srfi-e...@srfi.schemers.org

unread,
Sep 25, 2009, 4:24:56 AM9/25/09
to
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 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

Derick Eddington

unread,
Oct 20, 2009, 2:04:29 PM10/20/09
to
SRFI 103: Library Files has been substantially revised [1,2].
Feedback invited.

[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

Derick Eddington

unread,
Dec 12, 2009, 3:17:23 AM12/12/09
to
SRFI 103: Library Files has been substantially revised again [1,2].
Noteworthy changes are that multiple Scheme dialects are supported
(instead of only R6RS) and that file name extensions are
configurable. It is now more useful and a little simpler.

Feedback invited.

[1] http://srfi.schemers.org/srfi-103/srfi-103.html
[2] http://srfi.schemers.org/srfi-103/mail-archive/msg00080.html

--
: Derick
----------------------------------------------------------------

Derick Eddington

unread,
Jan 9, 2010, 11:47:43 PM1/9/10
to
SRFI 103: Library Files is going to be revised again. Most of the
changes are minor improvements and uncontroversial (I assume). I need
feedback about a few undecided substantial changes: removing support
for an implicit file name, changing the encoding design to encoding of
code points instead of UTF-8, and requiring SRFI 104's parameters to
affect all systems. Please see:

http://srfi.schemers.org/srfi-103/mail-archive/msg00091.html

and respond there.

Thank you,

--
: Derick
----------------------------------------------------------------

Derick Eddington

unread,
Mar 5, 2010, 8:57:04 PM3/5/10
to
SRFI 103: Library Files has been substantially revised [1,2].
Noteworthy changes are:

- 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
----------------------------------------------------------------

0 new messages