Changeset 15464

Timestamp:

10/29/20 21:02:15 (3 years ago)

Author:

Mark Evenson

Message:

abcl 1.8.0 metadata

rc14

TODO manual needs much description about pathnames

Location:

trunk/abcl

Files:

• CHANGES (modified) (5 diffs)
• README (modified) (9 diffs)
• abcl.asd (modified) (1 diff)
• abcl.rdf (modified) (7 diffs)
• contrib/abcl-asdf/abcl-asdf-tests.asd (modified) (1 diff)
• contrib/abcl-asdf/abcl-asdf.asd (modified) (1 diff)
• contrib/abcl-asdf/asdf-mvn-module.asd (modified) (1 diff)
• contrib/abcl-introspect/abcl-introspect-test.asd (modified) (1 diff)
• contrib/abcl-introspect/abcl-introspect.asd (modified) (1 diff)
• contrib/asdf-jar/asdf-jar.asd (modified) (1 diff)
• contrib/jfli/README (modified) (1 diff)
• contrib/jfli/jfli.asd (modified) (1 diff)
• contrib/jss/jss.asd (modified) (1 diff)
• contrib/mvn/jna.asd (modified) (1 diff)
• contrib/pom.xml (modified) (1 diff)
• doc/design/pathnames/abcl-pathname.org (modified) (1 diff)
• doc/manual/abcl.bib (modified) (1 diff)
• doc/manual/abcl.tex (modified) (50 diffs)
• doc/manual/extensions.tex (modified) (3 diffs)
• doc/manual/java.tex (modified) (2 diffs)
• doc/manual/system.tex (modified) (8 diffs)
• doc/manual/threads.tex (modified) (8 diffs)
• doc/releng.org (modified) (6 diffs)
• pom.xml (modified) (1 diff)
• src/org/armedbear/lisp/Version.java (modified) (1 diff)
• src/org/armedbear/lisp/abcl-contrib.lisp (modified) (1 diff)

trunk/abcl/CHANGES

@@ -1 @@
-Version 1.7.2
+Version 1.8.0
 =============
 
-Unreleased
-
-<https://abcl.org/svn/trunk/abcl/>
+October 29, 2020
+
+<https://abcl.org/svn/tags/1.8.0/>
 <https://github.com/armedbear/abcl/>
 <https://gitlab.common-lisp.net/abcl/abcl/>
+
+Features
+--------
+
+* [r15390-r15406][r15408-r15413][r15422-r15425][r15434-r15458][r15460-15463]
+  Overhauled JAR-PATHNAME and URL-PATHNAME subtypes of PATHNAME to fully support
+  recursive addressing of zip within both local and remote zip
+  archives.
+
+Incompatibilities
+-----------------
+
+* [r15414] Change algorithm for determining pathname type from
+  parsing namestrings to be more like SBCL and CCL
+
+     | Expression | NAME   | TYPE |
+     |------------+--------+------|
+     | #p"..."    | ".."   | ""   |
+     | #p".foo"   | ".foo" | NIL  |
+
+Enhancements
+------------
+
+* [r15378][r15421] Support openjdk15 
+
+* [r15360-r15365] (Alessio) Serialization of top-level, named functions.
+
+* [r15353] JAVA:JCLASS now works on all arrays of primitive type.
+
+* [r15356] ABCL-INTROSPECT adds EXT:READ-CLASS to conveniently read
+  java class bytes from the source referenced by a PATHNAME.
+
+* [r15366] The compiler now properly emits make-array for top-level specialized
+  vector forms.
+
+* [r15367] Loading ABCL-INTROSPECT now adds the function
+  EXT:STREAM-UNIX-FD which returns the integer of the underlying file
+  descriptor from a socket stream reference.
+
+* [r15368] Less cryptic warnings for ignored socket write timeout.
+
+* [r15381] JNEW-ARRAY-FROM-ARRAY now capable of constructing all
+  possible arrays of primitive type.
+
+
+Fixes
+-----
+
+* [r15359] Fix running openjdk11 compilation on openjdk8.
+
+* [r15358] Fix SYS:RUN-PROGRAM issues with openjdk11.
+
+* [r15357] Re-work strategy for the denotation of the hosting runtime
+  platform in CL:*FEATURES* to include a "JAVA-<n>" where "<n>" is an
+  integer denoting the major version of the platform according to
+  JEP-223.
+
+* [r15351][r15352] For CL:MAKE-ARRAY, ensure :NIO-BUFFER argument
+  works in all cases, fix :NIO-DIRECT for (unsigned-byte 16)
+  specialized arrays.
+
+* [r15369][r15376] Fix wildcard matching to work on pathnames
+  consisting of only #\* characters.
+
+* [r15377] (Daniel Kochmański) Fix loop destructuring problems.
+
+* [r15379] Fix VECTOR-PUSH-EXTEND for (UNSIGNED-BYTE 8).
+
+* [r15427] Define CALL-NEXT-METHOD and NEXT-METHOD-P as local functions.
+
+* [r15386] Make the pre-compiler be more careful in optimizing lambdas.
+
+* [r15388] Ensure that SYS:CHECK-REDEFINITION does not signal error
+  conditions.
+
+* [r15387] Fix FILE-POSITION by resetting file charset decoder before
+  conversion.
+
+* [r15383] Fix capacity allocation for arrays specialized on
+
+         (or (unsigned-byte 16)
+             (unsigned-byte 32))
+
+  created via an CL:MAKE-ARRAY :NIO-BUFFER argument.
+
+
+Contrib
+-------
+
+* [r15420] Use jna-5.6.0.
+
+* [r15384] quicklisp-abcl attempts to remove all Quicklisp fasls on
+  failure to load.
+
+* ASDF-JAR loading compiled fasls stored in JAR archives
+  now works again.
+
+
+Build
+-----
+
+* [r15426] Ensure that we construct the manual with a proper version.
+
+* [r15407] Building and running a local ABCL hopefully does more of
+  what you mean.
+
+
+Tests
+-----
+
+* [r15416] The default reporting via abcl/test/lisp/parse-ansi-tests is
+  for compiled tests.
+
+* [r15385] Travis CI now uses versions of STATIC-VECTORS, CL+SSL, and
+  CFFI from Quicklisp.  Overhaul ABCL-PROVE system definition
+  explicitly enumerating tests for more deterministic behavior.
+
+* [r15382] Test usage of :NIO-BUFFER keyword in CL:MAKE-ARRAY.
+
+* [r15380] Tests for creating primitive java arrays.
 
 
@@ -21 +141 @@
 -----
 
-[r15337] Fix ELT on vectors specialized on (unsigned-byte 32)
-
-[r15327] Restore svref optimizations for SIMPLE-VECTOR sorts
-
-[r15326] Fix sorting vectors of length 0
+* [r15337] Fix ELT on vectors specialized on (unsigned-byte 32)
+
+* [r15327] Restore svref optimizations for SIMPLE-VECTOR sorts
+
+* [r15326] Fix sorting vectors of length 0
 
 
@@ -74 +194 @@
    greater than 2^32-1 now properly signals a type error.
      
-* [r15267] ABCL-BUILD:ANT/CALL no longer signals an error on failure instead
-  reporting associated error messages.
+* [r15267] ABCL-BUILD:ANT/CALL no longer signals an error on failure
+  instead reporting associated error messages.
 
 * [r15281] Autoconfiguration for builds on supported platforms extended.
@@ -86 +206 @@
   Travis.
 
-
 Tests
 -----
@@ -92 +211 @@
 * [r15277] (pdietz) Additional tests for compiler failures.
 
-* [r15278][r15279] (phoe) Added tests for unbound slots DIVISION-BY-ZERO has
-  ARITHMETIC-ERROR-OPERANDS.
-
-* [r15284][r15285][r15288] The CI now tests the ability to use OpenSSL via
-  CL+SSL.
+* [r15278][r15279] (phoe) Added tests for unbound slots
+  DIVISION-BY-ZERO has ARITHMETIC-ERROR-OPERANDS.
+
+* [r15284][r15285][r15288] The CI now tests the ability to use OpenSSL
+  via CL+SSL.
 
 * [r15289] The CI now tests the version CFFI with

trunk/abcl/README

@@ -50 +50 @@
 
     illin:~/work/abcl$ docker run -it YOURID/abcl
-    Armed Bear Common Lisp 1.7.1
-    Java 11.0.7 AdoptOpenJDK    
+    Armed Bear Common Lisp 1.8.0
+    Java 11.0.8 AdoptOpenJDK
     OpenJDK 64-Bit Server VM
     Low-level initialization completed in 0.295 seconds.
@@ -57 +57 @@
     Type ":help" for a list of available commands.
     CL-USER(1): (lisp-implementation-version)
-    "1.7.1"
-    "OpenJDK_64-Bit_Server_VM-AdoptOpenJDK-11.0.7+10"
-    "x86_64-Mac_OS_X-10.15.5"
+    "1.8.0"
+    "OpenJDK_64-Bit_Server_VM-AdoptOpenJDK-11.0.8+10"
+    "x86_64-Mac_OS_X-10.15.7"
 
 To install Quicklisp for ABCL in the Docker container run:
@@ -79 +79 @@
 [abcl.org][abcl.org-release] archive unpack it into its own
 directory. To run ABCL directly from this directory, make sure the
-Java executable (`java`) (Java 6, 7, 8, 11, 13, and 14 are supported
-by ABCL 1.7.1) is in your shell's path.
-
-[maven-abcl]:          <https://mvnrepository.com/artifact/org.abcl/abcl/1.7.1>
-[maven-abcl-contrib]:  <https://mvnrepository.com/artifact/org.abcl/abcl-contrib/1.7.1>
-[abcl.org-release]:    <http://abcl.org/releases/1.7.1/>
+Java executable (`java`) (Java 6, 7, 8, 11, 13, 14, and 15 are
+supported by ABCL 1.7.0) is in your shell's path.
+
+[maven-abcl]:          <https://mvnrepository.com/artifact/org.abcl/abcl/1.8.0>
+[maven-abcl-contrib]:  <https://mvnrepository.com/artifact/org.abcl/abcl-contrib/1.8.0>
+[abcl.org-release]:    <http://abcl.org/releases/1.8.0/>
 
 To start ABCL, simply issue the following command:
@@ -92 +92 @@
 which should result in output like the following
 
-    Armed Bear Common Lisp 1.7.1
-    Java 1.8.0_252 AdoptOpenJDK
+    Armed Bear Common Lisp 1.8.0
+    Java 11.0.8 AdoptOpenJDK
     OpenJDK 64-Bit Server VM
     Low-level initialization completed in 0.222 seconds.
@@ -126 +126 @@
 tool.
 
-To build, one must have a Java 6, 7, 8, 11, 13 or 14 Java Development
-Kit (openjdk) installed locally. Just the Java Runtime Environment
-(JRE) isn't enough, as you need the Java compiler ('javac') to compile
-the Java source of the ABCL implementation.
+To build, one must have a Java 6, 7, 8, 11, 13, 14 or 15 Java
+Development Kit (openjdk) installed locally. Just the Java Runtime
+Environment (JRE) isn't enough, as you need the Java compiler
+('javac') to compile the Java source of the ABCL implementation.
 
 Download a binary distribution [Ant version 1.7.1 or greater][ant].
@@ -160 +160 @@
 
 Currently supported platforms are 'openjdk6', 'openjdk7', 'openjdk8',
-'openjdk11', 'openjdk13', and 'openjdk14'.
+'openjdk11', 'openjdk13', 'openjdk14', and 'openjdk15'.
 
 
@@ -192 +192 @@
 implementation.
 
-[manual]: https://abcl.org/releases/1.7.1/abcl-1.7.1.pdf
+[manual]: https://abcl.org/releases/1.8.0/abcl-1.8.0.pdf
 
 
@@ -198 +198 @@
 -----
 
-ABCL 1.7.1 currently fails ~45-46 out of 21848 total tests, whereas ABCL
+ABCL 1.8.0 currently fails ~49 out of 21848 total tests, whereas ABCL
 1.5.0 failed 48 out of 21708 total tests in the [revised and expanded
 ANSI CL test suite][ansi-test] (derived from the tests originally
@@ -245 +245 @@
     vibhu
 
-András Simon
+    András Simon
     Peter Graves
 
 Have fun!
 
-July 2020
+October 2020

trunk/abcl/abcl.asd

@@ -1 +1 @@
 ;;; -*- Mode: LISP; Syntax: COMMON-LISP -*-
 (defsystem abcl
-  :version "1.7.1"
+  :version "1.8.0"
   :in-order-to ((test-op (test-op "abcl/test/lisp"))))
 
 (defsystem abcl/test/lisp
-  :version "1.7.1"
+  :version "1.8.0"
   :description "Test ABCL with the its own collection of unit tests."
   :perform  (test-op (o s)

trunk/abcl/abcl.rdf

@@ -17 +17 @@
 <> 
   abcl:branch           <http://abcl.org/svn/trunk/abcl> ;
-  dc:identifier         <urn:abcl.org/1.7.2#dev> ; # deprecated?
-  dc:identifier         <urn:abcl.org/release/1.7.1#dev> ;
+  dc:identifier         <urn:abcl.org/1.8.0#> ; # deprecated?
+  dc:identifier         <urn:abcl.org/release/1.8.0#> ;
   doap:language        "Common Lisp" ;
   dc:created           "01-JAN-2004" ;
-  dc:modified          "18-JUL-2020" ;
-  dc:version           "abcl-1.7.2" ;
-  dc:release           "dev" ;
+  dc:modified          "28-OCT-2020" ;
+  dc:version           "abcl-1.8.0" ;
+  dc:release           "rc12" ;
   abcl:git             <https://github.com/armedbear/abcl/> ;
   abcl:git             <https://gitlab.common-lisp.net/abcl/abcl/> ;
@@ -94 +94 @@
      dc:license <http://usefulinc.com/doap/licenses/gplv2-classpath-exception> ;
      dc:licenseDocument 
-       <http://abcl.org/svn/tags/1.7.1/src/org/armedbear/COPYING> ;
+       <http://abcl.org/svn/tags/1.8.0/src/org/armedbear/COPYING> ;
 ] .
 
 doap:Project rdfs:seeAlso [
   a rdf:Bag;
-  rdf:_0 <http://abcl.org/releases/1.7.1/abcl-1.7.1.jar> ;
+  rdf:_0 <http://abcl.org/releases/1.8.0/abcl-1.8.0.jar> ;
   rdf:_1 <http://abcl.org/trac/timeline> ;
   rdf:_2 <http://abcl.org/trac/wiki> ;
@@ -122 +122 @@
      rdf:_17 <http://abcl.org/releases/1.6.0/abcl-1.7.0.jar> ;
      rdf:_19 <http://abcl.org/releases/1.6.0/abcl-1.7.1.jar> ;
+     rdf:_23 <http://abcl.org/releases/1.6.0/abcl-1.8.0.jar> ;
   ] ;
 ] .
@@ -161 +162 @@
 
 abcl:jna
-        dc:version "5.5.0" .
+        dc:version "5.6.0" .
 abcl:asdf
         dc:version "3.3.4" .
@@ -192 +193 @@
   rdf:_13  openjdk:13 ;
   rdf:_14  openjdk:14 ;
+  rdf:_15  openjdk:15 ;
   rdfs:comment "Compatible Java runtimes" .
 
@@ -205 +207 @@
 [abcl:build _:options]
     not.org:target "1.8" ;
-    not.org:source "1.6" ;
+#    not.org:source "1.6" ;
     not.org:encoding "UTF-8" ;
     not.org:debug "true" ;
@@ -221 +223 @@
    rdf:_13  openjdk:13 ;
    rdf:_14  openjdk:14 ;
+   rdf:_14  openjdk:15 ;
    rdfs:comment "Supported build platforms" .
 

trunk/abcl/contrib/abcl-asdf/abcl-asdf-tests.asd

@@ -3 +3 @@
 (defsystem abcl-asdf-tests
   :author "Mark Evenson"
-  :long-description "<urn:abcl.org/release/1.7.1/contrib/abcl-asdf/test#>"
+  :long-description "<urn:abcl.org/release/1.8.0/contrib/abcl-asdf/test#>"
   :version "2.1.0"
   :defsystem-depends-on (prove-asdf)

trunk/abcl/contrib/abcl-asdf/abcl-asdf.asd

@@ -3 +3 @@
   :author "Mark Evenson"
   :description "Extensions to ASDF for handling Java binary artifacts."
-  :long-description "<urn:abcl.org/release/1.7.1/contrib/abcl-asdf#>"
+  :long-description "<urn:abcl.org/release/1.8.0/contrib/abcl-asdf#>"
   :version "2.1.0"
   :depends-on (jss abcl-build)

trunk/abcl/contrib/abcl-asdf/asdf-mvn-module.asd

@@ -5 +5 @@
     :depends-on (jss abcl-asdf)
     :description "Handles Maven artifact exclusions via the ADSF:MVN-MODULE component."
-    :long-description "<urn:abcl.org/release/1.7.1/contrib/abcl-asdf/mvn-module#>"
+    :long-description "<urn:abcl.org/release/1.8.0/contrib/abcl-asdf/mvn-module#>"
     :version "1.0.0"
     :in-order-to ((test-op (test-op asdf-mvn-module-tests)))

trunk/abcl/contrib/abcl-introspect/abcl-introspect-test.asd

@@ -3 +3 @@
 (defsystem abcl-introspect-test
   :author "Mark Evenson"
-  :long-description "<urn:abcl.org/release/1.7.1/contrib/abcl-introspect/test#>"
+  :long-description "<urn:abcl.org/release/1.8.0/contrib/abcl-introspect/test#>"
   :version "2.0.0"
   :defsystem-depends-on (prove-asdf)

trunk/abcl/contrib/abcl-introspect/abcl-introspect.asd

@@ -3 +3 @@
   :author ("Alan Ruttenberg" "Mark Evenson")
   :description "Introspection on compiled function to aid source location and other debugging functions."
-  :long-description "<urn:abcl.org/release/1.7.1/contrib/abcl-introspect#>"
+  :long-description "<urn:abcl.org/release/1.8.0/contrib/abcl-introspect#>"
   :version "2.0.0"
   :depends-on (jss)

trunk/abcl/contrib/asdf-jar/asdf-jar.asd

@@ -3 +3 @@
   :author "Mark Evenson"
   :description "Packaging ASDF systems into jar files"
-  :long-description "<urn:abcl.org/release/1.7.1/contrib/asdf-jar#>"
+  :long-description "<urn:abcl.org/release/1.8.0/contrib/asdf-jar#>"
   :version "0.3.2"
   :components ((:module base

trunk/abcl/contrib/jfli/README

@@ -37 +37 @@
 # Colophon
 
-    <> abcl:documents <urn:abcl.org/release/1.7.1/contrib/jfli#0.2.0> .
+    <> abcl:documents <urn:abcl.org/release/1.8.0/contrib/jfli#0.2.0> .

trunk/abcl/contrib/jfli/jfli.asd

@@ -1 +1 @@
 ;;;; -*- Mode: LISP -*-
 (defsystem jfli
-  :long-description "<urn:abcl.org/release/1.7.1/contrib/jfli#>"
+  :long-description "<urn:abcl.org/release/1.8.0/contrib/jfli#>"
   :version "0.2.0"
   :components ((:file "jfli")))

trunk/abcl/contrib/jss/jss.asd

@@ -2 +2 @@
 (defsystem jss
   :author "Alan Ruttenberg, Mark Evenson"
-  :long-description "<urn:abcl.org/release/1.7.1/contrib/jss#>"
+  :long-description "<urn:abcl.org/release/1.8.0/contrib/jss#>"
   :version "3.6.0" 
   :components ((:module base 

trunk/abcl/contrib/mvn/jna.asd

@@ -3 +3 @@
 ;;;; Need to have jna.jar present for CFFI to work.
 (defsystem jna 
-  :long-description  "<urn:abcl.org/release/1.7.1/contrib/jna#5.6.0>"
+  :long-description  "<urn:abcl.org/release/1.8.0/contrib/jna#5.6.0>"
   :version "5.6.0"
   :defsystem-depends-on (jss abcl-asdf)

trunk/abcl/contrib/pom.xml

@@ -14 +14 @@
   <groupId>org.abcl</groupId>
   <artifactId>abcl-contrib</artifactId>
-  <version>1.7.2-SNAPSHOT</version>
+  <version>1.8.0</version>
   <packaging>jar</packaging>
   <name>Armed Bear Common Lisp (ABCL) Contribs</name>

trunk/abcl/doc/design/pathnames/abcl-pathname.org

@@ -395 +395 @@
 
 
-* Re-introducing relative URL-PATHNAME for 'file' scheme
-
-URIs don't allow relative pathnames, so to be more strict I
-implemented stripped out the abilty to create relative URL-PATHNAMEs.
-
 
 

trunk/abcl/doc/manual/abcl.bib

@@ -119 +119 @@
   note = {Last accessed Oct 2, 2016},
   }
-  

trunk/abcl/doc/manual/abcl.tex

@@ -10 +10 @@
 \begin{document}
 \title{Armed Bear Common Lisp User Manual}
-\date{Version 1.7.2\\
+\date{Version 1.8.0\\
 \smallskip
-Unreleased}
+October 2020}
 \author{Mark Evenson \and Erik H\"{u}lsmann \and Rudolf Schlatte \and
   Alessio Stalla \and Ville Voutilainen}
@@ -19 +19 @@
 
 \tableofcontents
+
+%%Preface to the first edition, abcl-1.0
+\subsection{Preface to the First Edition}
+\textsc{ABCL} 1.0 was released at the European Common Lisp Meeting
+in Amsterdam in 2011.
+
 %%Preface to the second edition, abcl-1.1
 \subsection{Preface to the Second Edition}
@@ -35 +41 @@
 \textsc{ABCL} 1.3 now implements an optimized implementation of the
 \code{org.armedbear.lisp.LispStack} abstraction thanks to Dmitry
-Nadezhin which runs on ORCL \textsc{JVMs} from 1.[5-8] conformantly.
+Nadezhin which runs on ORCL \textsc{JVMs} from \textsc{Java 5} through
+\textsc{Java 8}.
 
 %%Preface to the Fifth edition, abcl-1.4
@@ -68 +75 @@
 The User may need to use the facilities of the \textsc{ABCL-BUILD} contrib to
 recompile the implementation locally in more exotic runtimes (see
-Section~\ref{sec:abcl-build} page~\pageref{sec:abcl-build}).
+Section~\ref{section:abcl-build} page~\pageref{section:abcl-build}).
 
 
 %%Preface to the Eighth edition, abcl-1.7
 \subsection{Preface to the Eighth Edition}
-Since the implementation now runs comfortably on openjdk6, openjdk7,
-openjdk8, openjdk11, and openjdk14, we take advantage of the presence
-of the \code{java.nio} package introduced in \textsc{Java 5}.  We have
+Since the implementation now runs comfortably on \textsc{openjdk6},
+\textsc{openjdk7}, \textsc{openjdk8}, \textsc{openjdk11}, and
+\textsc{openjdk14}, we take advantage of the presence of the
+\code{java.nio} package introduced in \textsc{Java 5}.  We have
 overhauled the implementation to use these abstractions for arrays
 specialized on commonly used unsigned-byte types, adding two
 additional keyword arguments useful in their construction to
-\code{cl:make-array}.\footnote{See \ref{sec:make-array} on page
-\pageref{sec:make-array}}.
+\code{cl:make-array}.\footnote{See \ref{section:make-array} on page
+\pageref{section:make-array}}.
+
+%%Preface to the Ninth edition, abcl-1.8
+\subsection{Preface to the Ninth Edition}
+With the Ninth Edition of the implementation we now support building
+and running with \textsc{openjdk15}.  This is intended as the last
+major release to support the \textsc{openjdk6}, \textsc{openjdk7}, and
+\textsc{openjdk8} platforms.
+
+The implementation of the \code{EXT:JAR-PATHNAME} and
+\code{EXT:URL-PATHNAME} subtypes of \code{cl:PATHNAME} has been fixed
+to the point that arbitrary references to \textsc{ZIP} archives within
+archives now work for most read-only operations (\code{CL:PROBE-FILE},
+\code{CL:TRUENAME}, \code{CL:OPEN}, \code{CL:LOAD},
+\code{CL:FILE-WRITE-DATE}, \code{CL:DIRECTORY}, and
+\code{CL:MERGE-PATHNAMES}).  The previous versions of the
+implementation relied on the ability for \code{java.net.URL} to open
+streams of an archive within an archive, behavior that was silently
+dropped after Java 5, and consequently hasn't worked on common
+platforms supported by the Bear in a long time.  This restores the
+feasibility of accessing fasls from within jar files \footnote{Examine
+the ASDF-JAR contrib in section \ref{section:asdf-jar} on page
+\pageref{section:asdf-jar} for a recipe for packaging and accessing
+such artifacts.}.
 
 \chapter{Introduction}
@@ -90 +121 @@
 compiler have a byte-code version of ``49.0''.}, with an efficiency
 that varies upon the hosting JVM implementation.  \textsc{ABCL}
-supports running on the Java 6, Java 7, Java 8, Java 11, Java 13, and
-Java 14 openjdk \textsc{JVM} implementations\footnote{As of April
-2020, the AdoptOpenJDK.net community \url{https://adoptopenjdk.net/}
-provides perhaps the easiest installation of unencumbered openjdk
-implementations}.
+supports building and running on the \textsc{Java 6}, \textsc{Java 7},
+\textsc{Java 8}, \textsc{Java 11}, \textsc{Java 13}, \textsc{Java 14}
+and \textsc{Java 15} openjdk platform \textsc{JVM}
+implementations\footnote{As of October 2020, the AdoptOpenJDK.net
+community \url{https://adoptopenjdk.net/} provides perhaps the easiest
+installation of unencumbered openjdk implementations}.
 
 Armed Bear provides the following integration methods for interfacing
@@ -100 +132 @@
 \begin{itemize}
 \item Lisp code can create Java objects and call their methods (see
-  Section~\ref{sec:lisp-java}, page~\pageref{sec:lisp-java}).
+  Section~\ref{section:lisp-java}, page~\pageref{section:lisp-java}).
 \item Java code can call Lisp functions and generic functions, either
-  directly (Section~\ref{sec:calling-lisp-from-java},
-  page~\pageref{sec:calling-lisp-from-java}) or via \texttt{JSR-223}
-  (Section~\ref{sec:java-scripting-api},
-  page~\pageref{sec:java-scripting-api}).
+  directly (Section~\ref{section:calling-lisp-from-java},
+  page~\pageref{section:calling-lisp-from-java}) or via \texttt{JSR-223}
+  (Section~\ref{section:java-scripting-api},
+  page~\pageref{section:java-scripting-api}).
 \item \code{jinterface-implementation} creates Lisp-side implementations
   of Java interfaces that can be used as listeners for Swing classes and
@@ -146 +178 @@
   not a device
").  A future version of the implementation may return
   to conformance by using the \code{HOST} value to reflect the type
-  explicitly.}
+  explicitly. See \ref{section:jar-pathname} on page
+  \pageref{section:jar-pathname} for further information.}
 
 \end{itemize}
@@ -191 +224 @@
 June 1991 with an added ``classpath-exception'' clause (see the file
 \texttt{COPYING} in the source distribution\footnote{See
-  \url{http://abcl.org/svn/trunk/tags/1.7.1/COPYING}} for the license,
+  \url{http://abcl.org/svn/trunk/tags/1.8.0/COPYING}} for the license,
 term 13 in the same file for the classpath exception).  This license
 broadly means that you must distribute the sources to \textsc{ABCL},
@@ -208 +241 @@
   in the dark years.}
 \item Alan Ruttenberg \texttt{Thanks for JSS.}
-\item Olof-Joachim Frahm  
-\item piso
+\item Olof-Joachim Frahm
+\item András Simon (piso)
 \item and of course \emph{Peter Graves}
 \end{itemize}
@@ -218 +251 @@
 
 \textsc{ABCL} is packaged as a single jar file usually named either
-\texttt{abcl.jar} or possibly something like \texttt{abcl-1.7.1.jar} if
+\texttt{abcl.jar} or possibly something like \texttt{abcl-1.8.0.jar} if
 using a versioned package on the local file-system from your system
 vendor.  This jar file can be executed from the command line to obtain a
@@ -297 +330 @@
 
 \section{Lisp to Java}
-\label{sec:lisp-java}
+\label{section:lisp-java}
 
 \textsc{ABCL} offers a number of mechanisms to interact with Java from its
@@ -334 +367 @@
 \item Dynamic dispatch using the method name and the call-specific
   arguments provided by finding the best match (see
-  Section~\ref{sec:param-matching-for-ffi}).
+  Section~\ref{section:param-matching-for-ffi}).
 \end{itemize}
 
@@ -452 +485 @@
 
 \subsubsection{Parameter matching for FFI dynamic dispatch}
-\label{sec:param-matching-for-ffi}
+\label{section:param-matching-for-ffi}
 
 The algorithm used to resolve the best matching method given the name
@@ -502 +535 @@
 
 \subsection{Calling Lisp from Java}
-\label{sec:calling-lisp-from-java}
+\label{section:calling-lisp-from-java}
 
 Note: the entire \textsc{ABCL} \textsc{Lisp} system implementation in
@@ -654 +687 @@
 \end{listing-java}
 
-A more Lispy way to iterate down a list is to use the `cdr()` access
+A more Lispy way to iterate down a list is to use the \code{cdr()} access
 function just as like one would traverse a list in Lisp:;
 
@@ -666 +699 @@
 
 \section{Java Scripting API (JSR-223)}
-\label{sec:java-scripting-api}
+\label{section:java-scripting-api}
 
 ABCL can be built with support for JSR-223~\cite{jsr-223}, which offers
@@ -716 +749 @@
 
 At start-up (i.e. when its constructor is invoked, as part of the
-static initialization phase of \code{AbclScriptEngineFactory}) the ABCL
-script engine attempts to load an "init file" from the classpath
-(\texttt{/abcl-script-config.lisp}). If present, this file can be used to
-customize the behavior of the engine, by setting a number of
-variables in the \code{ABCL-SCRIPT} package. Here is a list of the available
-variables:
+static initialization phase of \code{AbclScriptEngineFactory}) the
+ABCL script engine attempts to load an "init file" from the classpath
+(\texttt{/abcl-script-config.lisp}). If present, this file can be used
+to customize the behavior of the engine, by setting a number of
+variables in the \code{ABCL-SCRIPT} package. Here is a list of the
+available variables:
 
 \begin{description}
@@ -809 +842 @@
 and to obtain Lisp implementations of Java interfaces. This is only
 partially possible with Lisp since it has functions, but not methods -
-not in the traditional OO sense, at least, since Lisp methods are not
+not in the traditional Object Oriented sense, at least, since Lisp methods are not
 attached to objects but belong to generic functions. Thus, the method
 \code{invokeMethod()} is not implemented and throws an
@@ -848 +881 @@
   transformed in an idiomatic Lisp name (\code{javaMethodName} becomes
   \code{JAVA-METHOD-NAME}) and a symbol with that name is searched in
-  the package. If it exists and is fbound, the corresponding function
+  the package. If it exists and is \code{FBOUND}, the corresponding function
   will be called. Function signature is as the hash-table case.
 \end{itemize}
@@ -901 +934 @@
 \subsection{The THREADS Dictionary}
 
-The extensions for handling multithreaded execution are collected in
+The extensions for handling multi-threaded execution are collected in
 the \code{THREADS} package.  Most of the abstractions in Doug Lea's
 excellent \code{java.util.concurrent} packages may be manipulated
@@ -935 +968 @@
 \section{Compiler to Java Virtual Machine Bytecode}
 
-The \code{CL:COMPILE-FILE} interface emits a packed fasl\footnote{The
+The \code{CL:COMPILE-FILE} interface emits a packed fasl \footnote{The
 term ``fasl'' is short for ``fast loader'', which in \textsc{Common
   Lisp} implementations refers} format whose \code{CL:PATHNAME} has
-the \code{TYPE} ``abcl''.  Structurally, \textsc{ABCL}'s fasls are an
+the \code{TYPE} ``abcl''.  Structurally, \textsc{ABCL}'s fasls are
 operating system neutral byte archives packaged in the zip compression
 format which contain artifacts whose loading \code{CL:LOAD}
 understands.  Internally, our fasls contain a piece of Lisp that
 \code{CL:LOAD} interprets as instructions to load the Java classes
-emitted by the \textsc{ABCL} Lisp compiler.  These ``synthetic''
-classes have a JVM class file version of ``49.0''.
+emitted by the \textsc{ABCL} Lisp compiler.  The classes emitted by
+the \textsc{ABCL} compiler have a JVM class file version of ``49.0''.
 
 % TODO check on what the compiler is currently emitting
@@ -972 +1005 @@
 
 \section{Pathname}
-
-We implement an extension to the \code{CL:PATHNAME} that allows for
-the description and retrieval of resources named in a
-\textsc{URI} \footnote{A \textsc{URI} is essentially a superset of
-  what is commonly understood as a \textsc{URL} We sometimes use the
-  term URL as shorthand in describing the URL Pathnames, even though
-  the corresponding encoding is more akin to a URI as described in
-  RFC3986 \cite{rfc3986}.}  scheme that the \textsc{JVM}
-``understands''.  By definition, support is built-in into the JVM to
-access the ``http'' and ``https'' schemes but additional protocol
-handlers may be installed at runtime by having \textsc{JVM} symbols
-present in the \code{sun.net.protocol.dynamic} package. See
-\cite{maso2000} for more details.
-
-\textsc{ABCL} has created specializations of the ANSI
-\code{CL:PATHNAME} object to enable to use of \textsc{URI}s to address
-dynamically loaded resources for the JVM.  The \code{EXT:URL-PATHNAME}
-specialization has a corresponding \textsc{URI} whose canonical
-representation is defined to be the \code{NAMESTRING} of the
-\code{CL:PATHNAME}. The \code{EXT:JAR-PATHNAME} extension further
-specializes the the \code{EXT:URL-PATHNAME} to provide access to
-components of zip archives.  
+\index{PATHNAME}
+
+\textsc{ABCL} extends its implementation of \textsc{ANSI}
+\code{PATHNAME} objects in order to allow read-only access to sources
+of bytes available via URIs \footnote{A \textsc{URI} is essentially a
+super-set of what is commonly understood as a \textsc{URL}. We
+sometimes use the term URL as shorthand in describing the URL
+Pathnames, even though the corresponding encoding is more akin to a
+URI as described in RFC3986 \cite{rfc3986}.} and to enable the
+addressing of arbitrarily recursive entries within \textsc{ZIP}
+archives.  These implementation decisions are encapsulated by the
+specialization of \code{CL:PATHNAME} as the \code{EXT:URL-PATHNAME}
+and the \code{EXT:JAR-PATHNAME} types.
 
 % RDF description of type hierarchy 
 % TODO Render via some LaTeX mode for graphviz?
 \begin{verbatim}
-  @prefix rdfs:  <http://www.w3.org/2000/01/rdf-schema#> .
-  @prefix ext:   <http://abcl.org/cl/package/extensions/> .
-  @prefix cl:    <http://abcl.org/cl/package/common-lisp/> .
-  
-  <ext:jar-pathname>    rdfs:subClassOf <ext:url-pathname> .
-  <ext:url-pathname>    rdfs:subClassOf <cl:pathname> .
-  <cl:logical-pathname> rdfs:subClassOf <cl:pathname> .
+    @prefix rdfs:  <http://www.w3.org/2000/01/rdf-schema#> .
+    @prefix ext:   <http://abcl.org/cl/package/extensions/> .
+    @prefix cl:    <http://abcl.org/cl/package/common-lisp/> .
+   
+    <ext:jar-pathname>    rdfs:subClassOf <ext:url-pathname> .
+    <ext:url-pathname>    rdfs:subClassOf <cl:pathname> .
+    <cl:logical-pathname> rdfs:subClassOf <cl:pathname> .
 \end{verbatim}
 
+The \code{EXT:URL-PATHAME} object utilizes the standard \textsc{JVM}
+implementation of \code{java.net.URL} to access resources named by the
+``file'', ``http'', ``https'', ``jar'', and ``ftp'' schemes.
+Additional protocol handlers for other may be installed at runtime by
+having \textsc{JVM} symbols present in the
+\code{sun.net.protocol.dynamic}\footnote{See \cite{maso2000} for more
+details. \url{https://stackoverflow.com/questions/41784555/print-all-supported-url-schemes-in-java8}
+contains a more up-to-date description.}  The namestring of a
+\code{EXT:URL-PATHNAME} object is equivalent to the string
+serialization of its representation encoded via the ``percent
+encoding'' rules of URIs\footnote{See
+\url{https://url.spec.whatwg.org/\#percent-encoded-bytes} for a
+description of this process.}.
+
+The \code{EXT:JAR-PATHNAME} extension utilizes the specialization of
+\code{EXT:URL-PATHNAME} to provide access to components of
+\textsc{ZIP} archives, of which the \textsc{JAR} (Java ARchive) format
+is a super-set.  \footnote{JAR archive utilize the ZIP format for
+packing and compression adding procedures to add supporting metadata
+in a manifest which is standardized text file stored at a canonical
+location within the archive.}  \textsc{JAR} archives are typically
+used to aggregate many Java class files and associated metadata and
+resources (text, images, etc.) into one file for distribution.
+\textsc{ABCL} is typically packaged as a \textsc{JAR} archive and
+emits its fasls as \textsc{ZIP} files.
+
+Both the \code{EXT:URL-PATHNAME} and \code{EXT:JAR-PATHNAME}
+specializations may be broadly used anywhere a \code{CL:PATHNAME} is
+accepted with the general caveat that stream obtained via
+\code{CL:OPEN} on either sub-type cannot be the target of write
+operations.
+
+\subsubsection{URL-PATHNAME}
 \label{EXTENSIONS:URL-PATHNAME}
 \index{URL-PATHNAME}
 
-\label{EXTENSIONS:JAR-PATHNAME}
-\index{JAR-PATHNAME}
-
-Both the \code{EXT:URL-PATHNAME} and \code{EXT:JAR-PATHNAME} objects
-may be used anywhere a \code{CL:PATHNAME} is accepted with the
-following caveats:
-
-\begin{itemize}
-
-\item A stream obtained via \code{CL:OPEN} on a \code{CL:URL-PATHNAME}
-  cannot be the target of write operations.
-
-\index{URI}
-\item Any results of canonicalization procedures performed on the
-  \textsc{URI} via local or network resolutions are discarded between
-  attempts (i.e. the implementation does not attempt to cache the
-  results of current name resolution of the URI for underlying
-  resource unless it is requested to be resolved.)  Upon resolution,
-  any canonicalization procedures followed in resolving the resource
-  (e.g. following redirects) are discarded.  Users may programatically
-  initiate a new, local computation of the resolution of the resource
-  by applying the \code{CL:TRUENAME} function to a
-  \code{EXT:URL-PATHNAME} object.  Depending on the reliability and
-  properties of your local \textsc{REST} infrastructure, these results
-  may not necessarily be idempotent over time\footnote {See
-    \cite{uri-pathname} for the design and implementation notes for
-    the technical details}.  A future implementation may attempt to
-  expose an API to observer/customize the content negotiation
-  initiated during retrieval of the representation of a given
-  resource, which is currently handled at the application level.
-
-\end{itemize}
+A \code{URL-PATHNAME} denotes a source of bytes addressable by its
+corresponding namestring interpreted as a \textsc{URI}.
+
+A \code{EXT:URL-PATHNAME} always has a \code{HOST} component that is a
+property list.  The values of the \code{HOST} property list are always
+character strings.  The allowed keys have the following meanings:
+
+\begin{description}
+\item[:SCHEME] Scheme of URI ("http", "ftp", "bundle", etc.)
+\item[:AUTHORITY] Valid authority according to the URI scheme.  For
+  "http" this could be "example.org:8080". 
+\item[:QUERY] The query of the \textsc{URI} 
+\item[:FRAGMENT] The fragment portion of the \textsc{URI}
+\end{description}
+
+If the \textsc{:SCHEME} property is missing, it is assumed to be
+``file'' denoting a reference to a file on the local file-system and
+will be normalized as such in any pathname subjected to
+\code{TRUENAME} resolution.
+  
+In order to encapsulate the implementation decisions for these
+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 sub-type of a Pathname may
+be determined with the predicates \code{PATHNAME-URL-P} and
+\code{PATHNAME-JAR-P}.
+
+\label{EXTENSIONS:URL-PATHNAME-SCHEME}
+\index{URL-PATHNAME-SCHEME}
+
+\label{EXTENSIONS:URL-PATHNAME-FRAGMENT}
+\index{URL-PATHNAME-FRAGMENT}
+
+\label{EXTENSIONS:URL-PATHNAME-AUTHORITY}
+\index{URL-PATHNAME-AUTHORITY}
+
+\label{EXTENSIONS:PATHNAME-URL-P}
+\index{PATHNAME-URL-P}
+
+\label{EXTENSIONS:URL-PATHNAME-QUERY}
+\index{URL-PATHNAME-QUERY}
+
+Any results of canonicalization procedures performed on a object of
+type \code{EXT:URL-PATHNAME} via local or network resolutions
+discarded between attempts (i.e. the implementation does not attempt
+to cache the results of current name resolution of the URI for
+underlying resource unless it is requested to be resolved.)  Upon
+resolution, any canonicalization procedures followed in resolving the
+resource (e.g. following redirects) are discarded.  Users may
+programatically initiate a new, local computation of the resolution of
+the resource by applying the \code{CL:TRUENAME} function to a
+\code{EXT:URL-PATHNAME} object.  Depending on the reliability and
+properties of your local \textsc{REST} infrastructure, these results
+may not necessarily be idempotent over time\footnote {See
+\cite{uri-pathname} for the design and implementation notes for the
+technical details}.  A future implementation may attempt to expose an
+API to observer/customize the content negotiation initiated during
+retrieval of the representation of a given resource, which is
+currently handled at the application level.
 
 The implementation of \code{EXT:URL-PATHNAME} allows the \textsc{ABCL}
 user to dynamically load code from the network.  For example,
 \textsc{Quicklisp} (\cite{quicklisp}) may be completely installed from
-the \textsc{REPL} as the single form:
+the \textsc{REPL} to download and execute the Quicklisp setup code via:
 
 \begin{listing-lisp}
-  CL-USER> (load "http://beta.quicklisp.org/quicklisp.lisp")
+  CL-USER> (load "https://beta.quicklisp.org/quicklisp.lisp")
 \end{listing-lisp}
 
-will load and execute the Quicklisp setup code.
-
-The implementation currently breaks \textsc{ANSI} conformance by allowing the
-types able to be \code{CL:READ} for the \code{DEVICE} to return a possible \code{CONS} of
-\code{CL:PATHNAME} objects.  %% citation from CLHS needed.
-
-In order to ``smooth over'' the bit about types being \code{CL:READ}
-from \code{CL:PATHNAME} components, we extend the semantics for the
-usual PATHNAME merge semantics when \code{*DEFAULT-PATHNAME-DEFAULTS*}
-contains a \code{EXT:JAR-PATHNAME} with the ``do what I mean''
-algorithm described in \ref{section:conformance} on page
-\pageref{section:conformance}.
-
-%See \ref{_:quicklisp} on page \pageref{_:quicklisp}.
-
-\subsubsection{Implementation}
-
-The implementation of these extensions stores all the additional
-information in the \code{CL:PATHNAME} object itself in ways that while strictly
-speaking are conformant, nonetheless may trip up libraries that don't
-expect the following:
-
-\begin{itemize}
-\item \code{DEVICE} can be either a string denoting a drive letter
-  under \textsc{DOS} or a list of exactly one or two elements.  If
-  \code{DEVICE} is a list, it denotes a \code{EXT:JAR-PATHNAME}, with
-  the entries containing \code{CL:PATHNAME} objects which describe the
-  outer and (possibly inner) locations of the jar
-  archive \footnote{The case of inner and outer
-    \code{EXT:JAR-PATHNAME} \ref{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 A \code{EXT:URL-PATHNAME} always has a \code{HOST} component that is a
-  property list.  The values of the \code{HOST} property list are
-  always character strings.  The allowed keys have the following meanings:
-  \begin{description}
-  \item[:SCHEME] Scheme of URI ("http", "ftp", "bundle", etc.)
-  \item[:AUTHORITY] Valid authority according to the URI scheme.  For
-    "http" this could be "example.org:8080". 
-  \item[:QUERY] The query of the \textsc{URI} 
-  \item[:FRAGMENT] The fragment portion of the \textsc{URI}
-  \end{description}
-
-\item In order to encapsulate the implementation decisions for these
-  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
-  be determined with the predicates \code{PATHNAME-URL-P} and
-  \code{PATHNAME-JAR-P}.
-
-\label{EXTENSIONS:URL-PATHNAME-SCHEME}
-\index{URL-PATHNAME-SCHEME}
-
-\label{EXTENSIONS:URL-PATHNAME-FRAGMENT}
-\index{URL-PATHNAME-FRAGMENT}
-
-\label{EXTENSIONS:URL-PATHNAME-AUTHORITY}
-\index{URL-PATHNAME-AUTHORITY}
-
-\label{EXTENSIONS:PATHNAME-URL-P}
-\index{PATHNAME-URL-P}
-
-\label{EXTENSIONS:URL-PATHNAME-QUERY}
-\index{URL-PATHNAME-QUERY}
-
-\end{itemize}
+\label{section:jar-pathname}
+
+\subsubsection{JAR-PATHNAME}
+\label{section:JAR-PATHNAME}
+\index{JAR-PATHNAME}
+
+In \textsc{ABCL}, the \code{DEVICE} can be either a string either
+denoting a drive letter or a UNC mount under \textsc{DOS} or a list of
+one or more elements.  If \code{DEVICE} is a list, it denotes a
+\code{EXT:JAR-PATHNAME}.
+
+The implementation extends the \textsc{ANSI} specification with
+\textsc{EXT:JAR-PATHNAME} by utilizing its \code{DEVICE} to contain a
+list of pathnames denoting the location of and relative address within
+a \textsc{ZIP} archive.  The first member of this list will be a
+\code{EXT:URL-PATHNAME} designates the root source of bytes encoded
+via the \textsc{ZIP} compression algorithm.  This reference can either
+be to a file located on the local file-system or as a remote source
+via an stream-oriented messaging protocol such as \textsc{https}.  The
+remainder of the \code{DEVICE} list contains ``traditional''
+\code{CL:PATHNAME} objects denoting successive relative archive paths.
+This allows pathnames to reference an entry in an arbitrarily nested
+ZIP archives, which is the case when the an ABCL fasl is included in
+in a jar archive.
+ 
+In order to implement useful behavior of merging with pathname
+defaults, the implementation will contain the \code{:UNSPECIFIC}
+keyword in any truename that wasn't explicitly merging with a
+\code{EXT:JAR-PATHNAME}.  Therefore, the implementation extends the
+semantics for the usual merge semantics when
+\code{*DEFAULT-PATHNAME-DEFAULTS*} contains a \code{EXT:JAR-PATHNAME}
+with the ``do what I mean'' algorithm described in
+\ref{section:conformance} on page \pageref{section:conformance}.
+
+The namestring representation of \code{EXT:JAR-PATHNAME} references
+use successive ``jar'' prefixes and corresponding ``!'' suffixes to
+encapsulate successive locations.  Described broadly, a
+\code{EXT:JAR-PATHNAME} encapsulates the \textsc{URL} describing the
+location of the archive and a possible entry within that archive.
+
+\begin{verbatim}
+    jar:<url>!/[<entry>]
+\end{verbatim}
+
+The \textsc{URL} usually has the ``file'' scheme, but remote locations
+expressed in the ``https'' or ``http'' are also allowed.
+
+Subsequent entries within an archive are denoted via prefixing
+additional ``jar'' schemes and suffixing the associated path.
+\begin{verbatim}
+    jar:jar:<url>!/<entry0>!/[<entry1>]
+    jar:jar:jar:<url>!/<entry0>!/<entry1>!/[<entry2>]
+\end{verbatim}
+
 
 \section{Package-Local Nicknames}
-\label{sec:package-local-nicknames}
-
-ABCL allows giving packages local nicknames: they allow short and
+\label{section:package-local-nicknames}
+
+ABCL allows giving packages local nicknames which allow short and
 easy-to-use names to be used without fear of name conflict associated
-with normal nicknames.\footnote{Package-local nicknames were originally
-developed in SBCL.}
+with normal nicknames.\footnote{Package-local nicknames were
+originally developed in SBCL.}
 
 A local nickname is valid only when inside the package for which it
@@ -1219 +1290 @@
 \end{adjustwidth}
 
-
-         
 \section{Extensible Sequences}
 
@@ -1229 +1298 @@
 \code{java.util.List} contract.
 
-
 %% an Example of using java.util.Lisp in Lisp would be nice
 
@@ -1276 +1344 @@
 
 There is an additional syntax for specializing the parameter of a
-generic function on a java class, viz. \code{(java:jclass CLASS-STRING)}
-where \code{CLASS-STRING} is a string naming a Java class in dotted package
-form.
+generic function on a java class, viz. \code{(java:jclass
+  CLASS-STRING)} where \code{CLASS-STRING} is a string naming a Java
+class in dotted package form.
 
 For instance the following specialization would perhaps allow one to
@@ -1336 +1404 @@
 
 
-Note that this sequence is never output by the implementation.  Instead,
-the corresponding Unicode character is output for characters whose
-code is greater than 0x00ff.
+Note that that the reader escaped sequence is never output by the
+implementation.  Instead, the implementation emits the bytes
+corresponding Unicode character is output for characters whose code is
+greater than \code{0x00ff}.
 
 \section{Overloading of the CL:REQUIRE Mechanism}
 
-The \code{CL:REQUIRE} mechanism is overloaded by attaching these
-semantics to the execution of \code{REQUIRE} on the following symbols:
+The \code{CL:REQUIRE} mechanism is overloaded by attaching the
+following behavior to the execution of \code{REQUIRE} on these symbols:
 
 \begin{description}[style=nextline]
@@ -1360 +1429 @@
     \begin{description}[style=nextline]
 
-    \item[\code{abcl-asdf}] Functions for loading JVM artifacts
-        dynamically, hooking into ASDF 3 objects where possible.  See
-        \ref{sec:abcl-asdf} on page \pageref{sec:abcl-asdf}.
-
-      \item[\code{asdf-jar}] Package addressable JVM artifacts via
-        \code{abcl-asdf} descriptions as a single binary artifact
-        including recursive dependencies.  See \ref{sec:asdf-jar} on
-        page \pageref{sec:asdf-jar}.
-
-      \item[\code{jna}] Allows dynamic access to specify Java Native
-        Interface (JNI) facility providing C-linkage to shared objects
-        by dynamically loading the 'jna.jar' artifact via
-        Maven\footnote{This loading can be inhibited if, at runtime,
-        the Java class corresponding ``:classname'' clause of the
-        system definition is present.}
-
-      \item[\code{quicklisp-abcl}] Boot a local Quicklisp installation
-        via the ASDF:IRI type introduced via ABCL-ASDF.
-
-      \item[\code{jfli}] A descendant of Rich Hickey's pre-Clojure work
-        on the JVM.
-
-      \item[\code{jss}] Introduces dynamic inspection of present
-        symbols via the \code{SHARPSIGN-QUOTATION\_MARK} macros as
-        Java Syntax Sucks.  See \ref{section:jss} on page
-        \pageref{sections:jss} for more details.
-
-      \item[\code{abcl-introspect}] Provides a framework for
-        introspecting runtime Java and Lisp object values.  Include
-        packaging for installing and using java decompilation tools
-        for use with \code{CL:DISASSEMBLE}.  See
-        \ref{section:abcl-introspect} on
-        \pageref{section:abcl-introspect} for futher information.
-        
-      \item[\code{abcl-build}] Provides a toolkit for building ABCL
-        from source, as well as installing the necessary tools for
-        such builds.  See \ref{section:abcl-build} on page
-        \pageref{section:abcl-build}.
-
-      \item[\code{named-readtables}] Provides a namespace for
-        readtables akin to the already-existing namespace of packages.
-        See \ref{section:named-readtables} on
-        \pageref{section:named-readtables} for further information.
+    \item[\code{abcl-asdf}] Functions for loading \textsc{JVM}
+      artifacts dynamically by extending \textsc{ASDF}.  See
+      \ref{section:abcl-asdf} on page \pageref{section:abcl-asdf}.
+
+    \item[\code{asdf-jar}] Package addressable \textsc{JVM} artifacts via
+      \code{abcl-asdf} descriptions as a single binary artifact
+      including recursive dependencies.  See \ref{sec:asdf-jar} on
+      page \pageref{section:asdf-jar}.
+
+    \item[\code{jna}] Allows the Java Native Interface
+      (\textsc{JNI}) facility to provide C-style linkage to other
+      operating system shared objects by dynamically loading the
+      'jna.jar' artifact via Maven\footnote{This loading can be
+      inhibited if, at runtime, the Java class corresponding
+      ``:classname'' clause of the system definition is present.}  
+
+    \item[\code{quicklisp-abcl}] Loads \textsc{Quicklisp} by
+      possibly initiating a network download via
+      \code{EXT:URL-PATHMAME}.
+
+    \item[\code{jfli}] A descendant of Rich Hickey's pre-Clojure
+      work on the JVM.
+
+    \item[\code{jss}] Introduces dynamic inspection of present
+      symbols via the \code{SHARPSIGN-QUOTATION\_MARK} macros as
+      Java Syntax Sucks.  See \ref{section:jss} on page
+      \pageref{sections:jss} for more details.
+
+    \item[\code{abcl-introspect}] Provides a framework for
+      introspecting runtime Java and Lisp object values.  Include
+      packaging for installing and using java decompilation tools
+      for use with \code{CL:DISASSEMBLE}.  See
+      \ref{section:abcl-introspect} on
+      \pageref{section:abcl-introspect} for further information.
+      
+    \item[\code{abcl-build}] Provides a toolkit for building ABCL
+      from source, as well as installing the necessary tools for
+      such builds.  See \ref{section:abcl-build} on page
+      \pageref{section:abcl-build}.
+
+    \item[\code{named-readtables}] Provides a namespace for
+      readtables akin to the already-existing namespace of packages.
+      See \ref{section:named-readtables} on
+      \pageref{section:named-readtables} for further information.
 
     \end{description}
@@ -1436 +1506 @@
 
 \section{Extension to CL:MAKE-ARRAY}
-\label{sec:make-array}
+\label{section:make-array}
+\index{MAKE-ARRAY}
 
 With the \code{:nio} feature is present\footnote{Available starting in
-abcl-1.7.1 and indicated by the presence of \code{:nio} in
-\code{cl:*features*}}, the implementation adds two keyword arguments
-to \code{cl:make-array}, viz. \code{:nio-buffer} and
+the Eighth Edition (aka abcl-1.7.0) and indicated by the presence of
+\code{:nio} in \code{cl:*features*}}, the implementation adds two
+keyword arguments to \code{cl:make-array}, viz. \code{:nio-buffer} and
 \code{:nio-direct}.
 
@@ -1490 +1561 @@
 primarily for large, long-lived buffers that are subject to the
 underlying system's native I/O operations. In general it is best to
-allocate direct buffers only when they yield a measureable gain in
+allocate direct buffers only when they yield a measurable gain in
 program performance.
 
@@ -1500 +1571 @@
 The \textsc{ABCL} contrib is packaged as a separate jar archive usually named
 \code{abcl-contrib.jar} or possibly something like
-\code{abcl-contrib-1.7.1.jar}.  The contrib jar is not loaded by the
+\code{abcl-contrib-1.8.0.jar}.  The contrib jar is not loaded by the
 implementation by default, and must be first initialized by the
 \code{REQUIRE} mechanism before using any specific contrib:
@@ -1509 +1580 @@
 
 \section{abcl-asdf}
-\label{sec:abcl-asdf}
+\label{section:abcl-asdf}
 \index{ABCL-ASDF}
 
 This contrib enables an additional syntax for \textsc{ASDF} system
 definition which dynamically loads \textsc{JVM} artifacts such as jar
-archives via encapsulation of the Maven build tool.  The Maven Aether
+archives via encapsulation by the Maven build tool.  The Maven Aether
 component can also be directly manipulated by the function associated
 with the \code{ABCL-ASDF:RESOLVE-DEPENDENCIES} symbol.
@@ -1523 +1594 @@
 
 
-When loaded, abcl-asdf adds the following objects to \textsc{ASDF}:
-\code{JAR-FILE}, \code{JAR-DIRECTORY}, \code{CLASS-FILE-DIRECTORY} and
-\code{MVN}, exporting them (and others) as public symbols.
+When loaded, \textsc{ABCL-ASDF} adds the following objects to
+\textsc{ASDF}: \code{JAR-FILE}, \code{JAR-DIRECTORY},
+\code{CLASS-FILE-DIRECTORY} and \code{MVN}, exporting them (and
+others) as public symbols.
 
 \subsection{Referencing Maven Artifacts via ASDF}
@@ -1547 +1619 @@
 
 We define an API for \textsc{ABCL-ASDF} as consisting of the following
-ASDF classes:
+\textsc{ASDF} classes:
 
 \code{JAR-DIRECTORY}, \code{JAR-FILE}, and
@@ -1554 +1626 @@
 
 Both the \code{MVN} and \code{IRI} classes descend from
-\code{ASDF-COMPONENT}, but do not directly have a filesystem location.
+\code{ASDF-COMPONENT}, but do not directly have a file-system location.
 
 For use outside of ASDF system definitions, we currently define one
@@ -1571 +1643 @@
                                          "gwt-user")
 WARNING: Using LATEST for unspecified version.
-"/Users/evenson/.m2/repository/com/google/gwt/gwt-user/2.4.0-rc1
-/gwt-user-2.4.0-rc1.jar:/Users/evenson/.m2/repository/javax/vali
-dation/validation-api/1.0.0.GA/validation-api-1.0.0.GA.jar:/User
-s/evenson/.m2/repository/javax/validation/validation-api/1.0.0.G
-A/validation-api-1.0.0.GA-sources.jar"
+"/Users/evenson/.m2/repository/com/google/gwt/gwt-user/2.9.0/gwt-user-2.9
+.0.jar:/Users/evenson/.m2/repository/com/google/jsinterop/jsinterop-annot
+ations/2.0.0/jsinterop-annotations-2.0.0.jar:/Users/evenson/.m2/repositor
+y/javax/validation/validation-api/1.0.0.GA/validation-api-1.0.0.GA.jar:/U
+sers/evenson/.m2/repository/javax/validation/validation-api/1.0.0.GA/vali
+dation-api-1.0.0.GA-sources.jar:/Users/evenson/.m2/repository/javax/servl
+et/javax.servlet-api/3.1.0/javax.servlet-api-3.1.0.jar:/Users/evenson/.m2
+/repository/org/w3c/css/sac/1.3/sac-1.3.jar"
 \end{listing-lisp}
 
-To actually load the dependency, use the \code{JAVA:ADD-TO-CLASSPATH} generic
-function:
+To actually load the dependency into the current process, use the
+\code{JAVA:ADD-TO-CLASSPATH} generic function:
 
 \begin{listing-lisp}
@@ -1591 +1666 @@
 
 More extensive documentations and examples can be found at
-\url{http://abcl.org/svn/tags/1.7.1/contrib/abcl-asdf/README.markdown}.
+\url{http://abcl.org/svn/tags/1.8.0/contrib/abcl-asdf/README.markdown}.
 
 \section{asdf-jar}
-\label{sec:asdf-jar}
+\label{section:asdf-jar}
 \index{ASDF-JAR}
 
@@ -1604 +1679 @@
 
 The documentation for this contrib can be found at
-\url{http://abcl.org/svn/tags/1.7.1/contrib/asdf-jar/README.markdown}.
+\url{http://abcl.org/svn/tags/1.8.0/contrib/asdf-jar/README.markdown}.
 
 \section{jss}
@@ -1610 +1685 @@
 \index{JSS}
 
-To one used to the more universal syntax of Lisp pairs upon which the
-definition of read and compile time macros is quite
+To one used to the more universal syntax of s-expr pairs upon which
+the definition of read and compile time macros is quite
 natural \footnote{See Graham's ``On Lisp''
-  http://lib.store.yahoo.net/lib/paulgraham/onlisp.pdf.}, the Java
-syntax available to the Java programmer may be said to suck.  To
-alleviate this situation, the JSS contrib introduces the
+http://lib.store.yahoo.net/lib/paulgraham/onlisp.pdf.}, the syntax
+available to the \textsc{Java} programmer may be said to suck.  To
+alleviate this situation, the \textsc{JSS} contrib introduces the
 \code{SHARPSIGN-DOUBLE-QUOTE} (\code{\#"}) reader macro, which allows
 the the specification of the name of invoking function as the first
@@ -1621 +1696 @@
 Lisp programmers seem to be wired to think.
 
-While quite useful, we don't expect that the JSS contrib will be the
-last experiment in wrangling Java from Common Lisp.
+While quite useful, we don't expect that the \textsc{JSS} contrib will
+be the last experiment in wrangling \textsc{Java} from \textsc{Common
+  Lisp}.
 
 \subsection{JSS usage}
 
-Example:
+An example of using \textsc{JSS} to enumerate the \textsc{Java}
+runtime system properties:
 
 \begin{listing-lisp}
@@ -1640 +1717 @@
 
 Some more information on jss can be found in its documentation at
-\url{http://abcl.org/svn/tags/1.7.1/contrib/jss/README.markdown}
+\url{http://abcl.org/svn/tags/1.8.0/contrib/jss/README.markdown}
 
 \section{jfli}
@@ -1649 +1726 @@
 from Common Lisp.
 
-\url{http://abcl.org/svn/tags/1.7.1/contrib/jfli/README}.
+\url{http://abcl.org/svn/tags/1.8.0/contrib/jfli/README}.
 
 \section{abcl-introspect}
-\ref{section:abcl-introspect}
+\label{section:abcl-introspect}
 \index{ABCL-INTROSPECT}
 
 \textsc{ABCL-INTROSPECT} offers more extensive functionality for
 inspecting the state of the implementation, most notably in
-integration with SLIME, where the backtrace mechanism is augmented to
-the point that local variables are inspectable.
-
-A compiled function is an instance of a class - This class has
-multiple instances if it represents a closure, or a single instance if
-it represents a non-closed-over function.
+integration with \textsc{SLIME}, where the backtrace mechanism is
+augmented to the point that local variables are inspectable.
+
+A compiled function is an instance of a class, which has multiple
+instances if it represents a closure, or a single instance if it
+represents a non-closed-over function.
 
 The \textsc{ABCL} compiler stores constants that are used in function
@@ -1674 +1751 @@
 uses them in at least two ways. First, to annotate locally defined
 functions with the top-level function they are defined within, and
-second to search for callers of a give function \footnote{ Since java
+second to search for callers of a give function \footnote{ Since \textsc{Java}
   functions are strings, local fields also have these strings. In the
   context of looking for callers of a function you can also give a
@@ -1698 +1775 @@
 \subsection{Implementations for CL:DISASSEMBLE}
 \label{abcl-introspect-disassemblers}
-
-The following ASDF systems packages various external tools that may be
+\index{CL:DISASSEMBLE}
+
+The following \textsc{ASDF} systems packages various external tools that may be
 selected by the \code{SYS:CHOOSE-DISASSEMBLER} interface:
 
@@ -1756 +1834 @@
   
 
-\url{http://abcl.org/svn/tags/1.7.1/contrib/abcl-introspect/}.
+\url{http://abcl.org/svn/tags/1.8.0/contrib/abcl-introspect/}.
 
 \section{abcl-build}
-\label{sec:abcl-build}
+\label{section:abcl-build}
 \index{ABCL-BUILD}
 
 
 \textsc{ABCL-BUILD} constitutes a new implementation for the original
-Lisp-hosted ABCL build system API in the package \code{ABCL-BUILD}
-that uses the same build artifacts as all of the other current builds.
-
-\subsection{Utilities}
+Lisp-hosted \textsc{ABCL} build system API in the package
+\code{ABCL-BUILD} that uses the same build artifacts as all of the
+other current builds.
+
+\subsection{ABCL-BUILD Utilities}
 
 \textsc{ABCL-BUILD} consolidates various utilities that are useful
 for system construction, namely
+
 \begin{itemize}
 
@@ -1785 +1865 @@
 \end{itemize}
 
-\url{http://abcl.org/svn/tags/1.7.1/contrib/abcl-build/}.
+\url{http://abcl.org/svn/tags/1.8.0/contrib/abcl-build/}.
 
 \section{named-readtables}
@@ -1794 +1874 @@
 readtables akin to the already-existing namespace of packages.
 
-Originally from \url{https://github.com/melisgl/named-readtables/}.
-
-See \url{http://abcl.org/svn/tags/1.7.1/contrib/named-readtables/} for
+This contrib was included from the source available from
+\url{https://github.com/melisgl/named-readtables/}.
+
+See \url{http://abcl.org/svn/tags/1.8.0/contrib/named-readtables/} for
 more information.
 
@@ -1813 +1894 @@
 
 In 2008, the implementation was transferred to the current
-maintainers, who have strived to improve its usability as a
+maintainers, who have striven to improve its usability as a
 contemporary Common Lisp implementation.
 
@@ -1836 +1917 @@
 community contributions from Vihbu, Olof, Pipping, and Cyrus.  We
 gingerly stepped into current century by establishing \textsc{git}
-bridges to the source repositories avaiable via the URIs
+bridges to the source repositories available via the URIs
 \url{https://github.com/armedbear/abcl/} and
 \url{https://gitlab.common-lisp.net/abcl/abcl/} so that pull requests
@@ -1856 +1937 @@
 abcl-1.7.1 as a maintenance release in July 2020.
 
+We released abcl-1.8.0 under the darkening storms of October 2020
+
+
 \appendix 
 
@@ -1865 +1949 @@
 
 The public interfaces in this package are subject to change with
-\textsc{ABCL} 1.8.
+\textsc{ABCL} 1.9
 
 \include{system}

trunk/abcl/doc/manual/extensions.tex

@@ -749 +749 @@
 
 \paragraph{}
+\label{EXTENSIONS:READ-CLASS}
+\index{READ-CLASS}
+--- Function: \textbf{read-class} [\textbf{extensions}] \textit{pathname}
+
+\begin{adjustwidth}{5em}{5em}
+Read the file at PATHNAME as a Java byte[] array
+\end{adjustwidth}
+
+\paragraph{}
 \label{EXTENSIONS:READ-TIMEOUT}
 \index{READ-TIMEOUT}
@@ -957 +966 @@
 
 \paragraph{}
+\label{EXTENSIONS:STREAM-UNIX-FD}
+\index{STREAM-UNIX-FD}
+--- Function: \textbf{stream-unix-fd} [\textbf{extensions}] \textit{stream}
+
+\begin{adjustwidth}{5em}{5em}
+Return the integer of the underlying unix file descriptor for STREAM
+
+Added by ABCL-INTROSPECT.
+\end{adjustwidth}
+
+\paragraph{}
 \label{EXTENSIONS:STRING-FIND}
 \index{STRING-FIND}
@@ -1092 +1112 @@
 
 \paragraph{}
+\label{EXTENSIONS:WRITE-CLASS}
+\index{WRITE-CLASS}
+--- Function: \textbf{write-class} [\textbf{extensions}] \textit{class-bytes pathname}
+
+\begin{adjustwidth}{5em}{5em}
+Write the Java byte[] array CLASS-BYTES to PATHNAME.
+\end{adjustwidth}
+
+\paragraph{}
 \label{EXTENSIONS:WRITE-TIMEOUT}
 \index{WRITE-TIMEOUT}

trunk/abcl/doc/manual/java.tex

@@ -218 +218 @@
 
 \begin{adjustwidth}{5em}{5em}
-not-documented
+Returns the cause of JAVA-EXCEPTION. (The cause is the Java Throwable
+  object that caused JAVA-EXCEPTION to be signalled.)
 \end{adjustwidth}
 
@@ -346 +347 @@
 
 \begin{adjustwidth}{5em}{5em}
-Returns the name of the Java class of OBJECT. If the NAME argument is
-  supplied, verifies that OBJECT is an instance of the named class. The name
-  of the class or nil is always returned as a second value.
+not-documented
 \end{adjustwidth}
 

trunk/abcl/doc/manual/system.tex

@@ -712 +712 @@
 
 \begin{adjustwidth}{5em}{5em}
-Methods of invoking CL:DISASSEMBLE consisting of a pushable list of (name function), where function takes a object to disassemble, returns the results as a string.
-
-The system is :jad using the venerable-but-still-works JAD. 
+Methods of invoking CL:DISASSEMBLE consisting of a enumeration of (keyword function) pairs
+
+The pairs (keyword function) contain a keyword identifying this
+particulat disassembler, and a symbol designating function takes a
+object to disassemble.
+
+Use SYS:CHOOSE-DISASSEMBLER to install a given disassembler as the one
+used by CL:DISASSEMBLE.  Additional disassemblers/decompilers are
+packaged in the ABCL-INTROSPECT contrib.
+
+The intial default is :javap using the javap command line tool which
+is part of the Java Developement Kit.
 
 \end{adjustwidth}
@@ -931 +940 @@
 
 \begin{adjustwidth}{5em}{5em}
-not-documented
+Signal simple-error when EXPR is non-NIL.
 \end{adjustwidth}
 
@@ -1012 +1021 @@
 
 \begin{adjustwidth}{5em}{5em}
-Hook to choose invoked behavior of CL:DISASSEMBLE by using one of the methods registered in SYSTEM:*DISASSEMBLERS*. 
-
-Optionally, prefer the strategy named NAME if one exists.
+Report current disassembler that would be used by CL:DISASSEMBLE
+
+With optional keyword NAME, select the associated disassembler from
+SYS:*DISASSEMBLERS*.
 \end{adjustwidth}
 
@@ -1027 +1037 @@
 
 \paragraph{}
+\label{SYSTEM:CLEAR-ZIP-CACHE}
+\index{CLEAR-ZIP-CACHE}
+--- Function: \textbf{clear-zip-cache} [\textbf{system}] \textit{}
+
+\begin{adjustwidth}{5em}{5em}
+not-documented
+\end{adjustwidth}
+
+\paragraph{}
 \label{SYSTEM:COERCE-TO-CONDITION}
 \index{COERCE-TO-CONDITION}
@@ -1261 +1280 @@
 
 \paragraph{}
-\label{SYSTEM:ENSURE-INPUT-STREAM}
-\index{ENSURE-INPUT-STREAM}
---- Function: \textbf{ensure-input-stream} [\textbf{system}] \textit{pathname}
-
-\begin{adjustwidth}{5em}{5em}
-Returns a java.io.InputStream for resource denoted by PATHNAME.
-\end{adjustwidth}
-
-\paragraph{}
 \label{SYSTEM:ENVIRONMENT}
 \index{ENVIRONMENT}
@@ -1525 +1535 @@
 
 \paragraph{}
+\label{SYSTEM:GET-INPUT-STREAM}
+\index{GET-INPUT-STREAM}
+--- Function: \textbf{get-input-stream} [\textbf{system}] \textit{pathname}
+
+\begin{adjustwidth}{5em}{5em}
+Returns a java.io.InputStream for resource denoted by PATHNAME.
+\end{adjustwidth}
+
+\paragraph{}
 \label{SYSTEM:GETHASH1}
 \index{GETHASH1}
@@ -1852 +1871 @@
 \label{SYSTEM:MAKE-FILE-STREAM}
 \index{MAKE-FILE-STREAM}
---- Function: \textbf{make-file-stream} [\textbf{system}] \textit{pathname namestring element-type direction if-exists external-format}
+--- Function: \textbf{make-file-stream} [\textbf{system}] \textit{pathname element-type direction if-exists external-format}
 
 \begin{adjustwidth}{5em}{5em}
@@ -1934 +1953 @@
 \index{MAKE-SYMBOL-MACRO}
 --- Function: \textbf{make-symbol-macro} [\textbf{system}] \textit{expansion}
+
+\begin{adjustwidth}{5em}{5em}
+not-documented
+\end{adjustwidth}
+
+\paragraph{}
+\label{SYSTEM:MATCH-WILD-JAR-PATHNAME}
+\index{MATCH-WILD-JAR-PATHNAME}
+--- Function: \textbf{match-wild-jar-pathname} [\textbf{system}] \textit{wild-jar-pathname}
 
 \begin{adjustwidth}{5em}{5em}

trunk/abcl/doc/manual/threads.tex

@@ -23 +23 @@
 
 \begin{adjustwidth}{5em}{5em}
-Acquires a lock on the `mutex'.
+Acquires the lock associated with the MUTEX
 \end{adjustwidth}
 
@@ -82 +82 @@
 \label{THREADS:MAKE-MAILBOX}
 \index{MAKE-MAILBOX}
---- Function: \textbf{make-mailbox} [\textbf{threads}] \textit{\&key ((queue g284829) NIL)}
+--- Function: \textbf{make-mailbox} [\textbf{threads}] \textit{\&key ((queue g305040) NIL)}
 
 \begin{adjustwidth}{5em}{5em}
@@ -91 +91 @@
 \label{THREADS:MAKE-MUTEX}
 \index{MAKE-MUTEX}
---- Function: \textbf{make-mutex} [\textbf{threads}] \textit{\&key ((in-use g285092) NIL)}
+--- Function: \textbf{make-mutex} [\textbf{threads}] \textit{\&key ((in-use g305303) NIL)}
 
 \begin{adjustwidth}{5em}{5em}
@@ -112 +112 @@
 
 \begin{adjustwidth}{5em}{5em}
-Returns an object to be used with the `with-thread-lock' macro.
+Returns an object to be used with the WITH-THREAD-LOCK macro.
 \end{adjustwidth}
 
@@ -165 +165 @@
 
 \begin{adjustwidth}{5em}{5em}
-Releases a lock on the `mutex'.
+Releases a lock associated with MUTEX
 \end{adjustwidth}
 
@@ -201 +201 @@
 
 \begin{adjustwidth}{5em}{5em}
-Waits for thread to finish.
+Waits for THREAD to die before resuming execution
+Returns the result of the joined thread as its primary value.
+Returns T if the joined thread finishes normally or NIL if it was interrupted.
 \end{adjustwidth}
 
@@ -228 +230 @@
 
 \begin{adjustwidth}{5em}{5em}
-Acquires a lock on `mutex', executes the body
-and releases the lock.
+Acquires a lock on MUTEX, executes BODY, and then releases the lock
 \end{adjustwidth}
 
@@ -238 +239 @@
 
 \begin{adjustwidth}{5em}{5em}
-Acquires a lock on the `lock', executes `body' and releases the lock.
+Acquires the LOCK, executes BODY and releases the LOCK
 \end{adjustwidth}
 

trunk/abcl/doc/releng.org

@@ -14 +14 @@
 
 Enter your "JIRA username and a password" in a
-<file:.m2/settings.xml>.  This will authenticate 
+<file:.m2/settings.xml>.  This will be used for authentication when
+the =mvn= tool uploads artifacts to the Sonatype snapshot and staging
+infrastructure.
 
 #+BEGIN_SRC xml
@@ -50 +52 @@
 
 **** Snapshots
-For snapshots - development versions - the version in the POM should look like ~x.y.z-SNAPSHOT~.
+For snapshots (aka development versions) the version in the POM should
+be of the form ~x.y.z-SNAPSHOT~.
 
 #+BEGIN_SRC bash
@@ -60 +63 @@
 #+END_SRC
 
-
 **** Release
-For releases - the version in the POM should look like  ~x.y.z~
+For releases the version in the POM should be of the form  ~x.y.z~
 
 #+BEGIN_SRC bash
-keyname='<evenson.not.org@gmail.com>'
-abcl_version=1.7.1
+keyname='<your_pgg_key@example.com>'
+abcl_version=1.8.0
 mvn gpg:sign-and-deploy-file -Dgpg.keyname=${keyname} -Dfile=dist/abcl.jar -DpomFile=pom.xml -Durl=https://oss.sonatype.org/service/local/staging/deploy/maven2/ -DrepositoryId=sonatype-nexus-staging
 mvn gpg:sign-and-deploy-file -Dgpg.keyname=${keyname} -Dfile=dist/abcl-${abcl_version}-sources.jar -DpomFile=pom.xml -Durl=https://oss.sonatype.org/service/local/staging/deploy/maven2/ -DrepositoryId=sonatype-nexus-staging -Dclassifier=sources
@@ -76 +78 @@
 #+BEGIN_SRC bash
 keyname='<evenson.not.org@gmail.com>'
-abcl_version=1.7.1
+abcl_version=1.8.0
 mvn gpg:sign-and-deploy-file -Dgpg.keyname=${keyname} -Dfile=dist/abcl-contrib.jar -DpomFile=contrib/pom.xml -Durl=https://oss.sonatype.org/service/local/staging/deploy/maven2/ -DrepositoryId=sonatype-nexus-staging 
 mvn gpg:sign-and-deploy-file -Dgpg.keyname=${keyname} -Dfile=dist/abcl-contrib-${abcl_version}-sources.jar -DpomFile=contrib/pom.xml -Durl=https://oss.sonatype.org/service/local/staging/deploy/maven2/ -DrepositoryId=sonatype-nexus-staging -Dclassifier=sources
@@ -100 +102 @@
 
 
-
 *** Specifying GPG executable
 
-For specifying gpg executable, use a property specified via
-'-Dgpg.executable=gpg2'.
+For specifying the =gpg= executable used via =mvn= use a property
+specified via the =gpg.executable= property (e.g. '-Dgpg.executable=gpg2'.)
 
 **** Signing binary release
@@ -123 +124 @@
   #+begin_example
   Created: ??
-  Revised: <2020-06-05 Fri 08:46>
+  Revised: <2020-10-21 Wed 10:01>
   #+end_example
   

trunk/abcl/pom.xml

@@ -14 +14 @@
   <groupId>org.abcl</groupId>
   <artifactId>abcl</artifactId>
-  <version>1.7.2-SNAPSHOT</version>
+  <version>1.8.0</version>
   <packaging>jar</packaging>
   <name>ABCL - Armed Bear Common Lisp</name>

trunk/abcl/src/org/armedbear/lisp/Version.java

@@ -42 +42 @@
   private Version() {}
   
-  static final String baseVersion = "1.7.2-dev";
+  static final String baseVersion = "1.8.0";
   
   static void init() {

trunk/abcl/src/org/armedbear/lisp/abcl-contrib.lisp

@@ -57 +57 @@
    ;; it would minimally need to check version information.
    (ignore-errors
-     (pathname "jar:https://abcl.org/releases/1.7.1/abcl.jar!/"))))
+     (pathname "jar:https://abcl.org/releases/1.8.0/abcl.jar!/"))))
 
 (defun flatten (list)