Changeset 13631

Timestamp:

10/19/11 20:08:47 (9 years ago)

Author:

Mark Evenson

Message:

Clean out all the mouse droppings from the corners.

Location:

trunk/abcl

Files:

• abcl.properties.in (modified) (2 diffs)
• doc/design/pathnames/pathnames.tex (modified) (1 diff)
• doc/slime.markdown (modified) (2 diffs)

trunk/abcl/abcl.properties.in

@@ -6 +6 @@
 #abcl.build.incremental=true
 
-# skips the compilation of Lisp sources in Netbeans (for debugging)
+# skips the compilation of Lisp sources in Netbeans 
+# (for debugging compiler-pass1.lisp and subsequent passes)
 #abcl.compile.lisp.skip=true
 
 # java.options sets the Java options in the abcl wrapper scripts
 
-# Examples
+# Examples:
 
-# set the JVM to use a maximum of 1GB of RAM (only works for 64bit JVMs)
+# Set the JVM to use a maximum of 1GB of RAM (only works for 64bit JVMs)
 #java.options=-d64 -Xmx1g
 
@@ -21 +22 @@
 #java.options=-d64 -XX:+CMSClassUnloadingEnabled -XX:MaxPermSize=1g
 
-# Additional site specific startup code to be merged in 'system.lisp'
+# Additional site specific startup code to be merged in 'system.lisp' at build time
 #abcl.startup.file=${basedir}/startup.lisp

trunk/abcl/doc/design/pathnames/pathnames.tex

@@ -14 +14 @@
 
 We implement the semantics for distributed resource description and
-retrieval by URL/URI/IRI Pathname in the Armeedbear Common Lisp implementation.
+retrieval by URL/URI/IRI Pathname in the Armed Bear Common Lisp
+implementation.
+
+\section{Plan of Attach}
+\subsection{Goals}
+
+\begin{enumerate]
+\item Use Common Lisp pathnames to refer to representations referenced
+  by a URL.
+
+\item The URL schemes supported shall include at least "http", and
+  those enabled by the URLStreamHandler extension mechanism.
+
+\item  Use URL schemes that are understood by the java.net.URL object.
+
+
+\item  MERGE-PATHNAMES 
+
+        (merge-pathnames "url.asd"
+            "http://example/org/armedbear/systems/pgp.asd")
+        ==> "http://example/org/armedbear/systems/url.asd"
+
+\item  PROBE-FILE returning the state of URL accesibility.
+
+\item  TRUENAME "aliased" to PROBE-FILE signalling an error if the URL is
+not accessible (see "Non-goal 1").
+
+\item  DIRECTORY works for non-wildcards.
+
+\item  URL pathname work as a valid argument for OPEN with :DIRECTION :INPUT.
+
+\item  Enable the loading of ASDF2 systems referenced by a URL pathname.
+
+\item  Pathnames constructed with the "file" scheme
+(i.e. #p"file:/this/file") need to be properly URI encoded according
+to RFC3986 or otherwise will signal FILE-ERROR.  
+
+\item.  The "file" scheme will continue to be represented by an
+"ordinary" Pathname.  Thus, after construction of a URL Pathname with
+the "file" scheme, the namestring of the resulting PATHNAME will no
+longer contain the "file:" prefix.
+
+\item.  The "jar" scheme will continue to be represented by a jar
+Pathname.
+\end{enumerate}
+
+\subsection{Non-goals}
+
+\begin{enumerate}
+
+\item We will not implement canonicalization of URL schemas (such as
+  following "http" redirects).
+
+\item \textsc{DIRECTORY} will not work for URL pathnames containing
+  wildcards.
+
+\end{enumerate}
+
+\subsubsection{Example}
+    Example of a Pathname specified by URL:
+    
+        #p"http://example.org/org/armedbear/systems/pgp.asd"
+    
+
 
 \section{Notes}

trunk/abcl/doc/slime.markdown

@@ -13 +13 @@
 ## Obtaining SLIME
 
-SLIME does not follow a release process in the standard, so you are
-best off with obtaining the [latest version from CVS][1]. [Daily
-snapshots as gzipped tarballs are also available][2].  Your local OS
-packaging system (i.e. MacPorts on OSX) may have a version as well.
+SLIME does not follow a release process in the standard sense with
+centrally versioned releases, so you are best off with obtaining the
+[latest version from CVS][1]. [Daily snapshots as gzipped tarballs are also available][2].
+Your local OS packaging system (i.e. MacPorts on OSX) may have a
+version as well.
 
 [1]: http://common-lisp.net/project/slime/#downloading
@@ -87 +88 @@
 
 
+### Historivia
+
+Luke Gorrie inherited a server implementation known as "Skank" which
+he rejected on the grounds of pure taste.
+