Changeset 13612
- Timestamp:
- 10/02/11 08:26:03 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/abcl/doc/manual/abcl.tex
r13610 r13612 6 6 \begin{document} 7 7 \title{A Manual for Armed Bear Common Lisp} 8 \date{ August 4, 2011}8 \date{October 2, 2011} 9 9 \author{Mark~Evenson, Erik~Huelsmann, Alessio~Stallo, Ville~Voutilainen} 10 10 … … 22 22 \chapter{Running} 23 23 24 ABCL is packaged as a single jar file (usually named either24 ABCL is packaged as a single jar file usually named either 25 25 ``abcl.jar'' or something like``abcl-0.28.0.jar'' if you are using a 26 versioned package) that can be executed under the 27 control of a suitable JVM as follows 26 versioned package from your system vendor. This byte archive can be 27 executed under the control of a suitable JVM by using the ``-jar'' 28 option to parse the manifest, and select the named class 29 (org.armedbear.lisp.Main) for excution: 28 30 29 31 \begin{listing-shell} … … 31 33 \end{listing-shell} 32 34 33 For this command to work, the ``java'' executable needs to be in your35 N.b. for this command to work, the ``java'' executable needs to be in your 34 36 path. 35 37 … … 233 235 234 236 If one is calling an primitive function in the CL package the syntax 235 becomes considerably simpler if we can locate the instance of236 definition in the ABCL source, we can invoke the symbol directly. To237 tell if a `LispObject` contains a reference to a symbol.237 becomes considerably simpler. If we can locate the instance of 238 definition in the ABCL Java source, we can invoke the symbol directly. 239 For instnace, to tell if a `LispObject` contains a reference to a symbol. 238 240 239 241 \begin{listing-java} 240 242 boolean nullp(LispObject object) { 241 243 LispObject result = Primitives.NULL.execute(object); 242 if (result == NIL) { 244 if (result == NIL) { // the symbol 'NIL' is explicity named in the Java 245 // namespace at ``Symbol.NIL'' 246 // but is always present in the 247 // localnamespace in its unadorned form for 248 // the convenience of the User. 243 249 return false; 244 250 } … … 264 270 \end{listing-java} 265 271 266 Although since in Lisp, any value other than NIL means "true", the 267 use of Java equality it quite a bit easier and more optimal: 272 Although since in Lisp, any value other than NIL means "true" 273 (so-called generalized Boolean), the use of Java equality it quite a 274 bit easier to type and more optimal in terms of information it conveys 275 to the compiler would be: 268 276 269 277 \begin{listing-java} … … 334 342 335 343 \section{Pathname} 344 345 We implment an extension to the Pathname that allows for the 346 description and retrieval of resources named in a URI scheme that the 347 JVM ``understands''. Support is built-in to the ``http'' and 348 ``https'' implementations but additional protocol handlers may be 349 installed at runtime by having JVM symbols present in the 350 sun.net.protocol.dynmamic pacakge. See [JAVA2006] for more details. 336 351 337 352 ABCL has created three specializations of the ANSI Pathname construct … … 420 435 contemporary Common Lisp implementation. 421 436 422 In 201x, with the publication of this Manual stating its confformance 423 to ANSI, we released abcl-1.0. 437 In 201x, with the publication of this Manual explicitly stating the 438 conformance of Armed Bear Common Lisp to ANSI, we release abcl-1.0. 439 440 \section{References} 441 442 [Java2000]: A New Era for Java Protocol Handlers. \url{http://java.sun.com/developer/onlineTraining/protocolhandlers} 424 443 425 444
Note: See TracChangeset
for help on using the changeset viewer.