Changeset 13612


Ignore:
Timestamp:
10/02/11 08:26:03 (10 years ago)
Author:
Mark Evenson
Message:

Edit for more consistent voice.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/abcl/doc/manual/abcl.tex

    r13610 r13612  
    66\begin{document}
    77\title{A Manual for Armed Bear Common Lisp}
    8 \date{August 4, 2011}
     8\date{October 2, 2011}
    99\author{Mark~Evenson, Erik~Huelsmann, Alessio~Stallo, Ville~Voutilainen}
    1010
     
    2222\chapter{Running}
    2323
    24 ABCL is packaged as a single jar file (usually named either
     24ABCL is packaged as a single jar file usually named either
    2525``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
     26versioned package from your system vendor.  This byte archive can be
     27executed under the control of a suitable JVM by using the ``-jar''
     28option to parse the manifest, and select the named class
     29(org.armedbear.lisp.Main) for excution:
    2830
    2931\begin{listing-shell}
     
    3133\end{listing-shell}
    3234
    33 For this command to work, the ``java'' executable needs to be in your
     35N.b. for this command to work, the ``java'' executable needs to be in your
    3436path.
    3537
     
    233235
    234236If one is calling an primitive function in the CL package the syntax
    235 becomes considerably simpler if we can locate the instance of
    236 definition in the ABCL source, we can invoke the symbol directly.  To
    237 tell if a `LispObject` contains a reference to a symbol.
     237becomes considerably simpler.  If we can locate the instance of
     238definition in the ABCL Java source, we can invoke the symbol directly.
     239For instnace, to tell if a `LispObject` contains a reference to a symbol.
    238240
    239241\begin{listing-java}
    240242    boolean nullp(LispObject object) {
    241243      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.
    243249        return false;
    244250      }
     
    264270\end{listing-java}
    265271
    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:
     272Although since in Lisp, any value other than NIL means "true"
     273(so-called generalized Boolean), the use of Java equality it quite a
     274bit easier to type and more optimal in terms of information it conveys
     275to the compiler would be:
    268276
    269277\begin{listing-java}
     
    334342
    335343\section{Pathname}
     344
     345We implment an extension to the Pathname that allows for the
     346description and retrieval of resources named in a URI scheme that the
     347JVM ``understands''.  Support is built-in to the ``http'' and
     348``https'' implementations but additional protocol handlers may be
     349installed at runtime by having JVM symbols present in the
     350sun.net.protocol.dynmamic pacakge. See [JAVA2006] for more details.
    336351
    337352ABCL has created three specializations of the ANSI Pathname construct
     
    420435contemporary Common Lisp implementation.
    421436
    422 In 201x, with the publication of this Manual stating its confformance
    423 to ANSI, we released abcl-1.0.
     437In 201x, with the publication of this Manual explicitly stating the
     438conformance 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}
    424443
    425444
Note: See TracChangeset for help on using the changeset viewer.