# Changeset 14516

Ignore:
Timestamp:
06/05/13 09:06:27 (9 years ago)
Message:

abcl-1.2.0: User manual refinements.

File:
1 edited

### Legend:

Unmodified
 r14515 %%Preface to the Third edition, abcl-1.2. \subsection{Preface to the Third Edition} THe implementation now contains a performant and conformant The implementation now contains a performant and conformant implementation of (A)MOP to the point of inclusion in CLOSER-MOP's test suite. of Java interfaces that can be used as listeners for Swing classes and similar. \item \code{java:jnew-runtime-class} can inject fully synthetic Java classes--and their objects-- into the current JVM process whose behavior is specified via closures expressed in Common Lisp.. \footnote{Parts of the current implementation are not fully finished, so the status of some interfaces here should be treated with skepticism if you run into problems.} \end{itemize} \textsc{ABCL} is supported by the Lisp library manager \index{URI} \item Any results of canonicalization procesures performed on the \item Any results of canonicalization procedures performed on the underlying \textsc{URI} are discarded between resolutions (i.e. the implementation does not attempt to cache the results of current name computation of the resolution of the resource by applying the \code{CL:TRUENAME} function to a \code{EXT:URL-PATHNAME} object. Depending on the reliablity and properties of your local Depending on the reliability and properties of your local \textsc{REST} infrastructure, these results may not necessarily be idempotent over time\footnote {See \cite{evenson2011} for the draft usual PATHNAME merge semantics when \code{*DEFAULT-PATHNAME-DEFAULTS*} contains a \code{EXT:JAR-PATHNAME} with the do what I mean'' algorithim described in \ref{section:conformance} on page algorithm described in \ref{section:conformance} on page \pageref{section:conformance}. outer and (possibly inner) locations of the jar archive \footnote{The case of inner and outer \code{EXT:EJAR-PATHNAME} arises when zip archives themselves \code{EXT:JAR-PATHNAME} arises when zip archives themselves contain zip archives which is the case when the ABCL fasl is included in the abcl.jar zip archive.}. \item In order to encapsulate the implementation decisions for these meanings, the following functions provide a setf-able API for meanings, the following functions provide a SETF-able API for reading and writing such values: \code{URL-PATHNAME-QUERY}, \code{URL-PATHNAME-FRAGMENT}, \code{URL-PATHNAME-AUTHORITY}, and \code{URL-PATHNAME-SCHEME}.  The specific subtype of a Pathname may \code{URL-PATHNAME-SCHEME}.  The specific sub-type of a Pathname may be determined with the predicates \code{PATHNAME-URL-P} and \code{PATHNAME-JAR-P}. \begin{adjustwidth}{5em}{5em} Returns an alist of \code{(local-nickname . actual-package)} Returns an ALIST of \code{(local-nickname . actual-package)} describing the nicknames local to the designated package. \section{ASDF} asdf-2.30 (see \cite{asdf}) is packaged as core component of \textsc{ABCL}, asdf-3.0.1 (see \cite{asdf}) is packaged as core component of \textsc{ABCL}, but not initialized by default, as it relies on the \textsc{CLOS} subsystem which can take a bit of time to start \footnote{While this time is