Changeset 13610
- Timestamp:
- 10/01/11 20:38:05 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/abcl/doc/manual/abcl.tex
r13580 r13610 18 18 19 19 \subsection{Version} 20 This manual corresponds to abcl-0.27.0, as yet unreleased. 21 20 This manual corresponds to abcl-0.28.0, as yet unreleased. 22 21 23 22 \chapter{Running} 24 23 25 24 ABCL is packaged as a single jar file (usually named either 26 ``abcl.jar'' or something like``abcl-0.2 7.1.jar'' if you are using a25 ``abcl.jar'' or something like``abcl-0.28.0.jar'' if you are using a 27 26 versioned package) that can be executed under the 28 27 control of a suitable JVM as follows 29 28 30 29 \begin{listing-shell} 31 cmd \$ java -jar abcl.jar30 cmd$ java -jar abcl.jar 32 31 \end{listing-shell} 33 32 … … 41 40 42 41 \begin{listing-shell} 43 cmd \$ abcl42 cmd$ abcl 44 43 \end{listing-shell} 45 44 … … 91 90 92 91 \begin{itemize} 93 \item Lack of long form of DEFINE-METHOD-COMBINATION94 92 \item Missing statement of conformance in accompanying documentation 93 \item The generic function sigatures of the DOCUMENTATION symbol do 94 not match the CLHS. 95 95 \end{itemize} 96 96 … … 102 102 expected of a contemporary Common Lisp. 103 103 \begin{itemize} 104 \item Incomplete MOP104 \item Incomplete (A)MOP 105 105 % N.B. 106 106 % TODO go through AMOP with symbols, starting by looking for … … 108 108 % XXX is this really blocking ANSI conformance? Answer: we have 109 109 % to start with such a ``census'' to determine what we have. 110 \item Incomplete Gray Streams 110 \item Incomplete Streams: need suitable abstraction between ANSI 111 and Gray streams. 112 111 113 \end{itemize} 112 114 … … 190 192 safer invocation pattern might be: 191 193 192 \begin{ code}[java]194 \begin{listing-java} 193 195 Interpreter interpreter = Interpreter.getInstance(); 194 196 if (interpreter == null) { 195 197 interpreter = Interpreter.createInstance(); 196 198 } 197 \end{code} 199 \end{listing-java} 200 198 201 199 202 The Lisp \code{eval} primitive may be simply passed strings for evaluation, … … 324 327 in working with the hosting JVM. 325 328 329 \section{Implementation Dependent} 330 \begin{enumerate} 331 \item Compiler to JVM 5 bytecode 332 \item Pathname extensionsn 333 \end{enumerate} 334 335 \section{Pathname} 336 337 ABCL has created three specializations of the ANSI Pathname construct 338 to enable to use of URIs to address dynamically loaded resources for 339 the JVM. 340 341 PATHNAME : URL-PATHNAME : JAR-PATHNAME 342 : LOGICAL-PATHNAME 343 344 Among other neat befits, this allows the ABCL user to laod dynamically 345 code from URIs like Quicklisp. 346 347 \begin{listing-lisp} 348 CL-USER> (load ''http://beta.quicklisp.org/quicklisp.lisp'') 349 \end{listing-lisp} 350 351 352 326 353 \section{Extensible Sequences} 327 328 354 329 355 \ref{RHODES2007} … … 394 420 contemporary Common Lisp implementation. 395 421 422 In 201x, with the publication of this Manual stating its confformance 423 to ANSI, we released abcl-1.0. 424 396 425 397 426 \end{document}
Note: See TracChangeset
for help on using the changeset viewer.