Ignore:
Timestamp:
06/21/11 10:11:10 (11 years ago)
Author:
Mark Evenson
Message:

Fix problems with whitespace in JAR-PATHNAME.

For dealing with URI Encoding (also known as [Percent Encoding]() we
implement the following rules which were implicitly.

[Percent Encoding]: http://en.wikipedia.org/wiki/Percent-encoding

  1. All pathname components are represented "as is" without escaping.
  1. Namestrings are suitably escaped if the Pathname is a URL-PATHNAME

or a JAR-PATHNAME.

  1. Namestrings should all "round-trip":

(when (typep p 'pathname)

(equal (namestring p)

(namestring (pathname p))))

Users may use EXT:URI-ENCODE and EXT:URI-DECODE to access the escaping
rules in circumstances where they wish to manipulate PATHNAME
namestrings more directly.

All tests in JAR-PATHNAMES now pass.

Constructors for PATHNAME now produce ERROR rather than FILE-ERROR as
CLHS says "The type file-error consists of error conditions that occur
during an attempt to open or close a file, or during some low-level
transactions with a file system," which doesn't apply here.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/abcl/doc/design/pathnames/jar-pathnames.markdown

    r13058 r13353  
    44    Mark Evenson
    55    Created:  09 JAN 2010
    6     Modified: 26 NOV 2010
     6    Modified: 21 JUN 2011
    77
    88Notes towards an implementation of "jar:" references to be contained
     
    270270       type: "lisp
    271271    }
     272
     273
     274URI Encoding
     275------------
     276
     277As a subtype of URL-PATHNAMES, JAR-PATHNAMES follow all the rules for
     278that type.  Most notably this means that all #\Space characters should
     279be encoded as '%20' when dealing with jar entries.
    272280
    273281
Note: See TracChangeset for help on using the changeset viewer.