Changeset 13631


Ignore:
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:
3 edited

Legend:

Unmodified
Added
Removed
  • trunk/abcl/abcl.properties.in

    r13339 r13631  
    66#abcl.build.incremental=true
    77
    8 # skips the compilation of Lisp sources in Netbeans (for debugging)
     8# skips the compilation of Lisp sources in Netbeans
     9# (for debugging compiler-pass1.lisp and subsequent passes)
    910#abcl.compile.lisp.skip=true
    1011
    1112# java.options sets the Java options in the abcl wrapper scripts
    1213
    13 # Examples
     14# Examples:
    1415
    15 # set the JVM to use a maximum of 1GB of RAM (only works for 64bit JVMs)
     16# Set the JVM to use a maximum of 1GB of RAM (only works for 64bit JVMs)
    1617#java.options=-d64 -Xmx1g
    1718
     
    2122#java.options=-d64 -XX:+CMSClassUnloadingEnabled -XX:MaxPermSize=1g
    2223
    23 # Additional site specific startup code to be merged in 'system.lisp'
     24# Additional site specific startup code to be merged in 'system.lisp' at build time
    2425#abcl.startup.file=${basedir}/startup.lisp
  • trunk/abcl/doc/design/pathnames/pathnames.tex

    r13611 r13631  
    1414
    1515We implement the semantics for distributed resource description and
    16 retrieval by URL/URI/IRI Pathname in the Armeedbear Common Lisp implementation.
     16retrieval by URL/URI/IRI Pathname in the Armed Bear Common Lisp
     17implementation.
     18
     19\section{Plan of Attach}
     20\subsection{Goals}
     21
     22\begin{enumerate]
     23\item Use Common Lisp pathnames to refer to representations referenced
     24  by a URL.
     25
     26\item The URL schemes supported shall include at least "http", and
     27  those enabled by the URLStreamHandler extension mechanism.
     28
     29\item  Use URL schemes that are understood by the java.net.URL object.
     30
     31
     32\item  MERGE-PATHNAMES
     33
     34        (merge-pathnames "url.asd"
     35            "http://example/org/armedbear/systems/pgp.asd")
     36        ==> "http://example/org/armedbear/systems/url.asd"
     37
     38\item  PROBE-FILE returning the state of URL accesibility.
     39
     40\item  TRUENAME "aliased" to PROBE-FILE signalling an error if the URL is
     41not accessible (see "Non-goal 1").
     42
     43\item  DIRECTORY works for non-wildcards.
     44
     45\item  URL pathname work as a valid argument for OPEN with :DIRECTION :INPUT.
     46
     47\item  Enable the loading of ASDF2 systems referenced by a URL pathname.
     48
     49\item  Pathnames constructed with the "file" scheme
     50(i.e. #p"file:/this/file") need to be properly URI encoded according
     51to RFC3986 or otherwise will signal FILE-ERROR. 
     52
     53\item.  The "file" scheme will continue to be represented by an
     54"ordinary" Pathname.  Thus, after construction of a URL Pathname with
     55the "file" scheme, the namestring of the resulting PATHNAME will no
     56longer contain the "file:" prefix.
     57
     58\item.  The "jar" scheme will continue to be represented by a jar
     59Pathname.
     60\end{enumerate}
     61
     62\subsection{Non-goals}
     63
     64\begin{enumerate}
     65
     66\item We will not implement canonicalization of URL schemas (such as
     67  following "http" redirects).
     68
     69\item \textsc{DIRECTORY} will not work for URL pathnames containing
     70  wildcards.
     71
     72\end{enumerate}
     73
     74\subsubsection{Example}
     75    Example of a Pathname specified by URL:
     76   
     77        #p"http://example.org/org/armedbear/systems/pgp.asd"
     78   
     79
    1780
    1881\section{Notes}
  • trunk/abcl/doc/slime.markdown

    r12560 r13631  
    1313## Obtaining SLIME
    1414
    15 SLIME does not follow a release process in the standard, so you are
    16 best off with obtaining the [latest version from CVS][1]. [Daily
    17 snapshots as gzipped tarballs are also available][2].  Your local OS
    18 packaging system (i.e. MacPorts on OSX) may have a version as well.
     15SLIME does not follow a release process in the standard sense with
     16centrally versioned releases, so you are best off with obtaining the
     17[latest version from CVS][1]. [Daily snapshots as gzipped tarballs are also available][2].
     18Your local OS packaging system (i.e. MacPorts on OSX) may have a
     19version as well.
    1920
    2021[1]: http://common-lisp.net/project/slime/#downloading
     
    8788
    8889
     90### Historivia
     91
     92Luke Gorrie inherited a server implementation known as "Skank" which
     93he rejected on the grounds of pure taste.
     94
Note: See TracChangeset for help on using the changeset viewer.