Changeset 14311
- Timestamp:
- 12/07/12 12:23:38 (8 years ago)
- Location:
- branches/1.1.x
- Files:
-
- 11 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/1.1.x/README
r14303 r14311 177 177 ==== 178 178 179 ABCL now has a manual stating its conformance to the ANSI standard, 180 providing a compliant and practical Common Lisp implementation. 181 179 182 ABCL is a conforming ANSI Common Lisp implementation. Any other 180 183 behavior should be reported as a bug. 181 184 182 ABCL now has a manual stating its conformance to the ANSI standard, 183 providing a compliant and practical Common Lisp implementation. 184 Because of this, 185 The secondary and tertiary values of CL:LISP-IMPLEMENTATION-VERSION 186 provide additional information about the exact JVM runtime which ABCL 187 finds itself hosted upon which may be especially useful when 188 discussing and tracking issues on the Internet. 185 189 186 190 -
branches/1.1.x/abcl.asd
r14281 r14311 115 115 :compile-tests nil)) 116 116 117 (defsystem :ansi-compiled :version "1.2 "118 :description "Test ABCL with the compiled ANSI tests. "117 (defsystem :ansi-compiled :version "1.2.0" 118 :description "Test ABCL with the compiled ANSI tests. <> asdf:defsystem <urn:abcl.org/release/1.1.0/ansi-compiled#1.2.0> ." 119 119 :depends-on (ansi-rt) 120 120 :components … … 131 131 132 132 (defsystem :cl-bench 133 :description "Test ABCL with CL-BENCH." 133 :description "Test ABCL with CL-BENCH. <> asdf:defsystem <urn:abcl.org/release/1.1.0/cl-bench#1.0.0> ." 134 :version "1.0.0" 134 135 :components ((:module cl-bench-package :pathname "../cl-bench/" 135 136 :components ((:file "defpackage"))) -
branches/1.1.x/abcl.rdf
r14303 r14311 1 1 # -*- Mode: n3 -*- 2 @prefix dc: <http://purl.org/dc/elements/1.1/> . 3 @prefix abcl: <https://abcl.org#> . 2 4 3 @prefix abcl: <https://abcl.org#> . 5 <> dc:version "abcl-1.1.0" . 6 <> abcl:release "rc-3" . 7 4 8 <> 5 9 abcl:is "W3C Turtle RDF serializations format" ; … … 21 25 doap:language "Common Lisp" ; 22 26 dc:created "01-JAN-2004" ; 23 dc:modified "0 6-DEC-2012" ;27 dc:modified "07-DEC-2012" ; 24 28 25 <<<<<<< local26 <> dc:version "abcl-1.1.0" .27 <> a abcl:releaseCandidate "rc-3" .28 =======29 29 dc:version "abcl-1.1.0" ; 30 30 abcl:releaseCandidate "rc-3" . 31 >>>>>>> other32 31 33 <<<<<<< local 34 <> rdfs:seeAlso <file:README> . 35 <> rdfs:seeAlso <file:MANUAL> . 36 <> rdfs:seeAlso <file:doc/manual/abcl.tex> . 37 ======= 38 <> 39 rdfs:seeAlso <README> ; 40 rdfs:seeAlso <file:doc/manual/abcl.tex> . 41 >>>>>>> other 32 <> rdfs:seeAlso [ 33 a rdf:Alt ; 34 rdf:_1 <file:README> ; 35 rdf:_2 <file:MANUAL> ; 36 rdf:_3 <file:doc/manual/abcl.tex> 37 ] . 38 42 39 43 40 @prefix dc: <http://purl.org/dc/elements/1.1/> . … … 126 123 <http://code.google.com/p/abcl-dynamic-install/> . 127 124 128 <> doap:packages 129 abcl:abcl-contrib ; 130 rdfs:seeAlso <file:contrib/README.markdown> . 125 <> doap:packages [ 126 a rdf:Alt; 127 rdf:_1 abcl:abcl ; 128 rdf:_2 abcl:abcl-contrib ; 129 rdf:_3 abcl:asdf-install ; 130 rdf:_4 abcl:jss ; 131 rdf:_5 abcl:jfli ; 132 rdf:_6 abcl:abcl-asdf ; 133 rdf:_7 abcl:jna ; 134 rdf:_8 abcl:asdf-jar 135 ] . 136 137 abcl:abcl-contrib 138 dc:identifier <urn:abcl.org/release/1.1.0/abcl-contrib#1.1.0> ; 139 rdfs:seeAlso <file:contrib/README.markdown> . 140 141 abcl:asdf-install 142 dc:identifier <urn:abcl.org/release/1.1.0/contrib/asdf-install#0.6.10.2> ; 143 rdfs:seeAlso <file:contrib/asdf-install/README> . -
branches/1.1.x/build.xml
r14291 r14311 651 651 <patternset id="abcl.dist.misc" 652 652 description="Additional includes in the source distributions relative to basedir"> 653 654 <include name="abcl.rdf"/> 653 655 <include name="build.xml"/> 654 656 <include name="abcl.properties.in"/> -
branches/1.1.x/contrib/abcl-asdf/README.markdown
r14301 r14311 162 162 #### Colophon 163 163 164 Mark <evenson.not.org@gmail.com>165 166 164 Created: 2011-01-01 167 165 Revised: 2012-12-06 166 167 <> dc:documentation <urn:abcl.org/release/1.1.0/abcl-contrib#1.1.0> . 168 168 169 -
branches/1.1.x/contrib/jss/README.markdown
r14301 r14311 129 129 130 130 abcl-contrib: http://svn.common-lisp.net/armedbear/trunk/abcl/contrib/ 131 132 # See Also 133 134 An earlier version of this software is used in[lsw2][] Semantic Web 135 package for dealing with OWL2 ontologies in RDF(S) and other 136 notations. 137 138 [lsw2]: http://code.google.com/p/lsw2/ 139 131 140 132 141 # Colophon -
branches/1.1.x/contrib/jss/jss.asd
r14301 r14311 3 3 :author "Alan Ruttenberg, Mark Evenson" 4 4 :version "3.0.5" 5 :description "<> asdf:defsystem <urn:abcl.org/release/1.1.0/contrib/jss#3.05" .5 :description "<> asdf:defsystem <urn:abcl.org/release/1.1.0/contrib/jss#3.05" 6 6 :components ((:module base 7 7 :pathname "" :serial t -
branches/1.1.x/contrib/pom.xml
r14269 r14311 2 2 <project 3 3 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" 4 xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 4 xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 5 xmlns:abcl="http://svn.common-lisp.net/armedbear/tags/1.1.0/abcl/abcl.rdf"> 5 6 6 7 <!-- NOT USABLE FOR BUILDS, only for installing into a repository! --> -
branches/1.1.x/doc/manual/abcl.tex
r14302 r14311 11 11 \date{Version 1.1.0\\ 12 12 \smallskip 13 December 5, 2012}13 December 7, 2012} 14 14 \author{Mark Evenson \and Erik H\"{u}lsmann \and Rudolf Schlatte \and 15 15 Alessio Stalla \and Ville Voutilainen} … … 23 23 \subsection{Preface to the Second Edition} 24 24 25 ABCL 1.1 now contains (A)MOP. We hope you enjoy! --The Mgmt. 25 \textsc{ABCL} 1.1 now contains (A)MOP. We hope you enjoy! 26 27 --The Mgmt. 26 28 27 29 \chapter{Introduction} 28 30 29 Armed Bear Common Lisp (ABCL) is an implementation of Common Lisp that 30 runs on the Java Virtual Machine. It compiles Common Lisp to Java 5 31 bytecode, providing the following integration methods for interfacing 32 with Java code and libraries: 31 Armed Bear Common Lisp (\textsc{ABCL}) is an implementation of Common 32 Lisp that runs on the Java Virtual Machine. It compiles Common Lisp 33 to Java 5 bytecode\footnote{The class file version is ``49.0''.} , 34 providing the following integration methods for interfacing with Java 35 code and libraries: 33 36 \begin{itemize} 34 37 \item Lisp code can create Java objects and call their methods (see … … 43 46 similar. 44 47 \end{itemize} 45 ABCLis supported by the Lisp library manager46 QuickLisp\footnote{\url{http://quicklisp.org/}} and can run many of the 47 programs and libraries provided therein out-of-the-box.48 \textsc{ABCL} is supported by the Lisp library manager 49 \textsc{QuickLisp} \footnote{\url{http://quicklisp.org/}} and can run 50 many of the programs and libraries provided therein out-of-the-box. 48 51 49 52 \section{Conformance} … … 51 54 52 55 \subsection{ANSI Common Lisp} 53 \textsc{ABCL} is currently a (non)-conforming ANSICommon Lisp56 \textsc{ABCL} is currently a (non)-conforming \textsc{ANSI} Common Lisp 54 57 implementation due to the following known issues: 55 58 56 59 \begin{itemize} 57 \item The generic function signatures of the \code{ DOCUMENTATION} symbol60 \item The generic function signatures of the \code{CL:DOCUMENTATION} symbol 58 61 do not match the specification. 59 \item The \code{ TIME} form does not return a proper \code{VALUES}62 \item The \code{CL:TIME} form does not return a proper \code{CL:VALUES} 60 63 environment to its caller. 61 \item When merging pathnames and the defaults point to a \code{JAR-PATHNAME}, 62 we set the \code{DEVICE} of the result to \code{:UNSPECIFIC} if the pathname to be 63 be merged does not contain a specified \code{DEVICE}, does not contain a 64 specified \code{HOST}, does contain a relative \code{DIRECTORY}, and we are 65 not running on a \textsc{MSFT} Windows platform.\footnote{The intent of this 66 rather arcane sounding deviation from conformance is so that the 67 result of a merge won't fill in a DEVICE with the wrong "default 64 \item When merging pathnames and the defaults point to a 65 \code{EXT:JAR-PATHNAME}, we set the \code{DEVICE} of the result to 66 \code{:UNSPECIFIC} if the pathname to be be merged does not contain 67 a specified \code{DEVICE}, does not contain a specified \code{HOST}, 68 does contain a relative \code{DIRECTORY}, and we are not running on 69 a \textsc{MSFT} Windows platform.\footnote{The intent of this rather 70 arcane sounding deviation from conformance is so that the result 71 of a merge won't fill in a \code{DEVICE} with the wrong "default 68 72 device for the host" in the sense of the fourth paragraph in the 69 CLHS description of MERGE-PATHNAMES (see in \cite{CLHS} the paragraph beginning70 "If the PATHNAME explicitly specifies a host and not a deviceâŠ").71 A future version of the implementation may return to conformance72 by using the \code{HOST} value to reflect the type explicitly.73 }73 \textsc{CLHS} description of MERGE-PATHNAMES (see in \cite{CLHS} 74 the paragraph beginning "If the PATHNAME explicitly specifies a 75 host and not a deviceâŠ"). A future version of the implementation 76 may return to conformance by using the \code{HOST} value to 77 reflect the type explicitly. } 74 78 75 79 \end{itemize} … … 81 85 are solicited. 82 86 83 ABCL aims to be be a fully conforming ANSI Common Lisp implementation. 84 Any other behavior should be reported as a bug.87 \textsc{ABCL} aims to be be a fully conforming \textsc{ANSI} Common 88 Lisp implementation. Any other behavior should be reported as a bug. 85 89 86 90 \subsection{Contemporary Common Lisp} 87 In addition to ANSIconformance, \textsc{ABCL} strives to implement91 In addition to \textsc{ANSI} conformance, \textsc{ABCL} strives to implement 88 92 features expected of a contemporary Common Lisp, i.e. a Lisp of the 89 93 post-2005 Renaissance. … … 98 102 computation at an arbitrarily selected call frame. 99 103 \item Incomplete streams abstraction, in that \textsc{ABCL} needs 100 suitable abstraction between ANSI and Gray streams. The streams could 101 be optimized to the JVM NIO abstractions at great profit for binary 102 byte-level manipulations. 103 \item Incomplete documentation (missing docstrings from exported symbols 104 and the draft status of this user manual). 104 suitable abstraction between \textsc{ANSI} and Gray 105 streams. \footnote{The streams could be optimized to the 106 \textsc{JVM} NIO \cite{nio} abstractions at great profit for 107 binary byte-level manipulations.} 108 \item Incomplete documentation (missing docstrings from exported 109 symbols and the draft status of this user manual). 105 110 \end{itemize} 106 111 … … 109 114 \section{License} 110 115 111 ABCL is licensed under the terms of the GPL v2 of June 1991 with the 112 ``classpath-exception'' (see the file \texttt{COPYING} in the source 113 distribution for the license, term 13 in the same file for the classpath 114 exception). This license broadly means that you must distribute the 115 sources to ABCL, including any changes you make, together with a program 116 that includes ABCL, but that you are not required to distribute the 117 sources of the whole program. Submitting your changes upstream to the 118 ABCL development team is actively encouraged and very much appreciated, 119 of course. 116 \textsc{ABCL} is licensed under the terms of the \textsc{GPL} v2 of 117 June 1991 with the ``classpath-exception'' (see the file 118 \texttt{COPYING} in the source distribution \footnote{See 119 \url{http://svn.common-lisp.net/armedbear/tags/1.1.0/abcl/COPYING}} for 120 the license, term 13 in the same file for the classpath exception). 121 This license broadly means that you must distribute the sources to 122 ABCL, including any changes you make, together with a program that 123 includes ABCL, but that you are not required to distribute the sources 124 of the whole program. Submitting your changes upstream to the ABCL 125 development team is actively encouraged and very much appreciated, of 126 course. 120 127 121 128 \section{Contributors} … … 131 138 132 139 140 133 141 \chapter{Running ABCL} 142 134 143 135 144 \textsc{ABCL} is packaged as a single jar file usually named either … … 137 146 using a versioned package on the local filesystem from your system 138 147 vendor. This jar file can be executed from the command line to obtain a 139 REPL\footnote{Read-Eval Print Loop, a Lisp command-line}, viz: 148 \textsc{REPL}\footnote{Read-Eval Print Loop, a Lisp command-line}, viz: 149 150 \index{REPL} 140 151 141 152 \begin{listing-shell} … … 157 168 158 169 Probably the easiest way of setting up an editing environment using the 159 Emacs editor is to use QuickLispand follow the instructions at170 \textsc{Emacs} editor is to use \textsc{QuickLisp} and follow the instructions at 160 171 \url{http://www.quicklisp.org/beta/#slime}. 161 172 … … 163 174 164 175 ABCL supports the following command line options: 176 177 \index{Command Line Options} 165 178 166 179 \begin{description} … … 174 187 \item[\texttt{ --batch}] evaluates forms specified by arguments and in 175 188 the initialization file \verb+~/.abclrc+, and then exits without 176 starting a REPL.189 starting a \textsc{REPL}. 177 190 \end{description} 178 191 … … 893 906 894 907 The implementation currently breaks \textsc{ANSI} conformance by allowing the 895 types able to be \code{CL:READ} for the \ var{DEVICE} to return a possible \code{CONS} of908 types able to be \code{CL:READ} for the \code{DEVICE} to return a possible \code{CONS} of 896 909 \code{CL:PATHNAME} objects. %% citation from CLHS needed. 897 910 … … 960 973 \section{Extensible Sequences} 961 974 962 See Rhodes2007 \cite{RHODES2007} for the design.963 964 975 The SEQUENCE package fully implements Christopher Rhodes' proposal for 965 976 extensible sequences. These user extensible sequences are used … … 968 979 \code{java.util.List} contract. 969 980 981 See Rhodes2007 \cite{RHODES2007} for the design. 982 970 983 %% an Example of using java.util.Lisp in Lisp would be nice 971 984 … … 988 1001 989 1002 Note that \code{(require 'java-collections)} must be issued before 990 \code{java.util.List} or any subclass is used as a specializer in a CLOS1003 \code{java.util.List} or any subclass is used as a specializer in a \textsc{CLOS} 991 1004 method definition (see the section below). 992 1005 … … 995 1008 \subsection{Metaobject Protocol} 996 1009 997 ABCL implements the metaobject protocol for CLOS as specified in AMOP. 998 The symbols are exported from the package \code{MOP}. 1010 \textsc{ABCL} implements the metaobject protocol for \textsc{CLOS} as 1011 specified in \textsc{(A)MOP}. The symbols are exported from the 1012 package \code{MOP}. 999 1013 1000 1014 \subsection{Specializing on Java classes} … … 1057 1071 \begin{description} 1058 1072 1059 \item{\code{ASDF}} Loads the \textsc{ASDF} implementation shipped 1073 \item{\code{ASDF}} 1074 Loads the \textsc{ASDF} implementation shipped 1060 1075 with the implementation. After \textsc{ASDF} has been loaded in 1061 1076 this manner, symbols passed to \code{CL:REQUIRE} which are … … 1066 1081 'cl-ppcre)}. 1067 1082 1068 \item{\code{ABCL-CONTRIB}} Locates and pushes the toplevel contents of 1083 \item{\code{ABCL-CONTRIB}} 1084 Locates and pushes the toplevel contents of 1069 1085 ``abcl-contrib.jar'' into the \textsc{ASDF} central registry. 1070 1086 1071 1087 \begin{enumerate} 1072 \item \code{abcl-asdf} 1073 Functions for loading JVM artifacts dynamically, hooking into ASDF 2 objects where possible. 1074 \item \code{asdf-jar} Package addressable JVM artifacts via 1088 \item \code{abcl-asdf} 1089 Functions for loading JVM artifacts 1090 dynamically, hooking into ASDF 2 objects where possible. 1091 \item \code{asdf-jar} 1092 Package addressable JVM artifacts via 1075 1093 \code{abcl-asdf} descriptions as a single binary artifact 1076 1094 including recursive dependencies. 1077 \item \code{mvn} 1078 These systems name common JVM artifacts from the distributed pom.xml graph of Maven Aether: 1095 \item \code{mvn} 1096 These systems name common JVM artifacts from 1097 the distributed pom.xml graph of Maven Aether: 1079 1098 \begin{enumerate} 1080 \item \code{jna} Dynamically load 'jna.jar' version 3.5.1 1099 \item \code{jna} 1100 Dynamically load 'jna.jar' version 3.5.1 1081 1101 from the network \footnote{This loading can be inhibited 1082 1102 if, at runtime, the Java class corresponding 1083 1103 ``:classname'' clause of the system defition is present.} 1084 1104 \end{enumerate} 1085 \item \code{quicklisp-abcl} (Not working) boot a local Quicklisp 1086 installation via the ASDF:IRI type introduced bia ABCL-ASDF. 1087 1088 \end{enumerate} 1105 \item \code{quicklisp-abcl} Boot a local Quicklisp installation 1106 via the ASDF:IRI type introduced bia ABCL-ASDF. 1107 1108 \begin{listing-lisp} 1109 CL-USER> (asdf:load-system :quicklisp-abcl :force t) 1110 \end{listing-lisp} 1111 1112 \end{enumerate} 1089 1113 1090 1114 \end{description} … … 1096 1120 can successful resolve the symbol. 1097 1121 1098 \section{JSS optionally extends the Reader}1122 \section{JSS extension of the Reader by SHARPSIGN-DOUBLE-QUOTE} 1099 1123 1100 1124 The JSS contrib consitutes an additional, optional extension to the … … 1105 1129 \section{ASDF} 1106 1130 1107 asdf-2.26.6 (see \cite{asdf}) is packaged as core component of ABCL,1108 but not initialized by default, as it relies on the CLOSsubsystem1131 asdf-2.26.6 (see \cite{asdf}) is packaged as core component of \textsc{ABCL}, 1132 but not initialized by default, as it relies on the \textsc{CLOS} subsystem 1109 1133 which can take a bit of time to start \footnote{While this time is 1110 1134 ``merely'' on the order of seconds for contemporary 2011 machines, 1111 1135 for applications that need to initialize quickly, for example a web 1112 server, this time might be unnecessarily long}. The packaged ASDF1136 server, this time might be unnecessarily long}. The packaged \textsc{ASDF} 1113 1137 may be loaded by the \textsc{ANSI} \code{REQUIRE} mechanism as 1114 1138 follows: … … 1120 1144 \chapter{Contrib} 1121 1145 1122 The ABCLcontrib is packaged as a separate jar archive usually named1146 The \textsc{ABCL} contrib is packaged as a separate jar archive usually named 1123 1147 \code{abcl-contrib.jar} or possibly something like 1124 1148 \code{abcl-contrib-1.1.0.jar}. The contrib jar is not loaded by the … … 1208 1232 locally from the network as well. 1209 1233 1234 More extensive documentations and examples can be found at 1235 \url{http://svn.common-lisp.net/armedbear/tags/1.1.0/abcl/contrib/abcl-asdf/README.markdown}. 1236 1237 1210 1238 \section{asdf-jar} 1211 1239 1212 The asdf-jar contrib provides a system for packaging ASDF systems into 1213 jar archives for ABCL. Given a running ABCL image with loadable ASDF 1214 systems the code in this package will recursively package all the 1215 required source and fasls in a jar archive. 1240 The asdf-jar contrib provides a system for packaging \textsc{ASDF} 1241 systems into jar archives for \textsc{ABCL}. Given a running 1242 \textsc{ABCL} image with loadable \textsc{ASDF} systems the code in 1243 this package will recursively package all the required source and 1244 fasls in a jar archive. 1216 1245 1217 1246 The documentation for this contrib can be found at 1218 \url{http://svn.common-lisp.net/armedbear/t runk/abcl/contrib/asdf-jar/README.markdown}.1247 \url{http://svn.common-lisp.net/armedbear/tags/1.1.0/abcl/contrib/asdf-jar/README.markdown}. 1219 1248 1220 1249 … … 1252 1281 1253 1282 Some more information on jss can be found in its documentation at 1254 \url{http://svn.common-lisp.net/armedbear/t runk/abcl/contrib/jss/README.markdown}1283 \url{http://svn.common-lisp.net/armedbear/tags/1.1.0/abcl/contrib/jss/README.markdown}. 1255 1284 1256 1285 \section{jfli} … … 1258 1287 1259 1288 The contrib contains a pure-Java version of JFLI. 1289 1290 \url{http://svn.common-lisp.net/armedbear/tags/1.1.0/abcl/contrib/jfli/README}. 1291 1260 1292 1261 1293 \section{asdf-install} … … 1271 1303 access. 1272 1304 1305 \url{http://svn.common-lisp.net/armedbear/tags/1.1.0/abcl/contrib/asdf-install/README}. 1306 1307 1273 1308 \chapter{History} 1309 \index{History} 1274 1310 1275 1311 \textsc{ABCL} was originally the extension language for the J editor, which was … … 1292 1328 on January 10, 2012. 1293 1329 1294 In December 2012, we revised the implementation by adding (A)MOP1330 In December 2012, we revised the implementation by adding \textsc{(A)MOP} 1295 1331 with the release of abcl-1.1.0. 1296 1332 … … 1304 1340 1305 1341 The public interfaces in this package are subject to change with 1306 ABCL1.2.1342 \textsc{ABCL} 1.2. 1307 1343 1308 1344 \include{system} … … 1313 1349 1314 1350 \include{jss} 1315 1316 1351 1317 1352 \bibliography{abcl} -
branches/1.1.x/maven-release.txt
r13756 r14311 1 1 # Releasing ABCL on Sonatype's OSS Maven repository - instructions 2 # 3 # WARNING: <file:pom.xml> and <file:contrib/pom.xml> are not currently valid descriptions of how to build ABCL. 4 # 5 # TODO Use the Maven Ant plugin to drive the standard build process. 2 6 # 3 7 # This assumes your settings.xml (/etc/maven2/settings.xml for Ubuntu-packaged Maven) contains something like this in its <servers></servers> section: -
branches/1.1.x/pom.xml
r14269 r14311 2 2 <project 3 3 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" 4 xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 4 xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 5 xmlns:abcl="http://svn.common-lisp.net/armedbear/tags/1.1.0/abcl/abcl.rdf"> 5 6 6 7 <!-- NOT USABLE FOR BUILDS, only for installing into a repository! -->
Note: See TracChangeset
for help on using the changeset viewer.