# Changeset 13798

Ignore:
Timestamp:
01/25/12 07:48:02 (10 years ago)
Message:

Merge User manual from what we tagged as 1.0.1

File:
1 edited

### Legend:

Unmodified
 r13749 \begin{document} \title{A Manual for Armed Bear Common Lisp} \date{January 10, 2012} \date{January 25, 2012} \author{Mark~Evenson, Erik~H\"{u}lsmann, Alessio~Stalla, Ville~Voutilainen} \subsection{Version} This manual corresponds to abcl-1.0.1 released on January 10, 2012. This manual corresponds to abcl-1.1.0-dev, as yet unreleased.. \subsection{License} \texttt{Thanks for JSS.} \item and of course \emph{Peter Graves} \textsc{ABCL} is packaged as a single jar file usually named either abcl.jar'' or possiblyabcl-1.0.1.jar'' if one is using a versioned package on the local filesytem from your system vendor.  This byte package on the local filesystem from your system vendor.  This byte archive can be executed under the control of a suitable JVM \footnote {Java Virtual Machine} by using the -jar'' option to parse the \item An incomplete implementation of a properly named metaobject protocol (viz. (A)MOP \footnote{The Art of the  Metaobject Protocol} ) protocol (c.f. the (A)MOP \footnote{The Art of the  Metaobject Protocol} specification) % N.b. ABCL can be built with support for JSR-223, which offers a language-agnostic API to invoke other languages from Java. The binary distribution downloadable from ABCL's common-lisp.net home is built distribution download-able from ABCL's common-lisp.net home is built with JSR-223 support. If you're building ABCL from source on a pre-1.6 JVM, you need to have a JSR-223 implementation in your CLASSPATH (such through ScriptEngineManager (refer to the javax.script documentation). \subsubsection{Startup and configuration file} At startup (i.e. when its constructor is invoked, as part of the \subsubsection{Start-up and configuration file} At start-up (i.e. when its constructor is invoked, as part of the static initialization phase of AbclScriptEngineFactory) the ABCL script engine attempts to load an "init file" from the classpath (/abcl-script-config.lisp). If present, this file can be used to customize the behaviour of the engine, by setting a number of customize the behavior of the engine, by setting a number of variables in the ABCL-SCRIPT package. Here is a list of the available variables: required source and fasls in a jar archive. \url{http://svn.common-lisp.net/armedbear/trunk/abcl/contrib/asdf-jar/README.markdown} See \url{http://svn.common-lisp.net/armedbear/trunk/abcl/contrib/asdf-jar/README.markdown}. \label{section:jss} To one used to a syntax that can construct macros the Java syntax may be said to suck, so we introduce the \code{SHARPSIGN-DOUBLE-QUOTE} \#" macro. To one used to the more universal syntax of Lisp pairs for which the definition of read and compile time macros is quite natural, the Java syntax available to the Java programmer may be said to suck.  To alleviate this situation, we introduce the \code{SHARPSIGN-DOUBLE-QUOTE} (\\#"Q'') macro, the first of perhaps many exper \subsection{JSS usage} \label{section:jss} Example: On October 22, 2011, with the publication of this Manual explicitly stating the conformance of Armed Bear Common Lisp to \textsc{ANSI}, we released abcl-1.0.0. released abcl-1.0.0.  We released abcl-1.0.1 as a maintainence release on January 10, 2012. \url{http://www.quicklisp.org/} \label{_:RHODES2007} \bibitem{Rhodes2007} Christopher Rhodes \url{http://jcsu.jesus.cam.ac.uk/~csr21/spec.pdf} \label{_:AMOP} \bibitem{AMOP} Gregor Kiczales, Jim de Rivieres, and Daniel G. Bobrow The Art of the Metaobject Protocol % XXX online citation \end{thebibliography}