Changeset 12523
- Timestamp:
- 03/11/10 08:42:48 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/abcl/doc/design/pathnames/abcl-jar-url.text
r12503 r12523 90 90 innermost. 91 91 92 * The DIRECTORY component of a JAR PATHNAME should be a list starting 93 with the :RELATIVE keyword, as hierarchial entries in jar files 94 are of the form "foo/bar/a.lisp" not "/foo/bar/a.lisp" 95 96 BNF 97 --- 98 99 An incomplete BNF of the syntax of JAR PATHNAME would be: 100 101 JAR-PATHNAME ::= "jar:" URL "!/" [ ENTRY ] 102 103 URL ::= <URL parsable via java.net.URL.URL()> 104 | JAR-FILE-PATHNAME 105 106 JAR-FILE-PATHNAME ::= "jar:" "file:" JAR-NAMESTRING "!/" [ ENTRY ] 107 108 JAR-NAMESTRING ::= ABSOLUTE-FILE-NAMESTRING 109 | RELATIVE-FILE-NAMESTRING 110 111 ENTRY ::= [ DIRECTORY "/"] * FILE 112 113 114 ### Notes 115 116 1. ABSOLUTE-FILE-NAMESTRING and RELATIVE-FILE-NAMESTRING use the 117 local filesystem conventions, meaning that on Windows this could 118 contain '\' as the directory separator, while an ENTRY always uses '/' 119 to separate directories within the jar proper. 92 120 93 121
Note: See TracChangeset
for help on using the changeset viewer.