Changeset 13649 for branches/1.0.x/abcl/doc/manual/abcl.tex
- Timestamp:
- 10/21/11 07:57:51 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/1.0.x/abcl/doc/manual/abcl.tex
r13648 r13649 19 19 \subsection{Version} 20 20 This manual corresponds to abcl-1.0.0, released on October 22, 2011. 21 22 \subsection{License} 23 24 The implementation is licensed under the terms of the GPL v2 of June 25 1991 with the ``classpath-exception'' that makes its deployment in 26 commercial settings quite reasonable. The license is viral in the 27 sense that if you change the implementation, and redistribute those 28 changes, you are required to provide the source to those changes back 29 to be merged with the public trunk. 21 30 22 31 \chapter{Running} … … 27 36 under the control of a suitable JVM by using the ``-jar'' option to 28 37 parse the manifest, and select the named class 29 (\code{org.armedbear.lisp.Main}) for execution :38 (\code{org.armedbear.lisp.Main}) for execution, viz: 30 39 31 40 \begin{listing-shell} … … 73 82 \end{verbatim} 74 83 75 All of the command line arguments which follow the occurrence of ``-- ''84 All of the command line arguments which follow the occurrence of ``----'' 76 85 are passed into a list bound to the EXT:*COMMAND-LINE-ARGUMENT-LIST* 77 86 variable. … … 91 100 92 101 \section{ANSI Common Lisp} 93 \textsc{ABCL} is currently a non-conforming ANSI Common Lisp implementation due94 to the followingissues:102 \textsc{ABCL} is currently a (non)-conforming ANSI Common Lisp 103 implementation due to the following known issues: 95 104 96 105 \begin{itemize} 97 106 \item The generic function signatures of the DOCUMENTATION symbol do 98 107 not match the CLHS. 99 \item The TIME form does not return a proper VALUES to its caller. 108 \item The TIME form does not return a proper VALUES environment to 109 its caller. 100 110 \end{itemize} 101 111 102 Somewhat confusingly, this statement of non-conformance 103 in theaccompanying user documentation fullfills the requirements that112 Somewhat confusingly, this statement of non-conformance in the 113 accompanying user documentation fullfills the requirements that 104 114 \textsc{ABCL} is a conforming ANSI Common Lisp implementation 105 115 according to the CLHS \footnote{Common Lisp Hyperspec language … … 861 871 We implement a special hexadecimal escape sequence for specifying 862 872 characters to the Lisp reader, namely we allow a sequences of the form 863 \# \textbackslash Uxxxx to be processed by the reader as character whose code is 864 specified by the hexadecimal digits ``xxxx''. The hexadecimal sequence 865 must be exactly four digits long, padded by leading zeros for values 866 less than 0x1000. 873 \# \textbackslash Uxxxx to be processed by the reader as character 874 whose code is specified by the hexadecimal digits ``xxxx''. The 875 hexadecimal sequence must be exactly four digits long \footnote{This 876 represents a compromise with contemporary in 2011 32bit hosting 877 architecures for which we wish to make text processing efficient. 878 Should the User require more control over UNICODE processing we 879 recommend Edi Weisz' excellent work with FLEXI-STREAMS which we 880 fully support}, padded by leading zeros for values less than 0x1000. 867 881 868 882 Note that this sequence is never output by the implementation. Instead,
Note: See TracChangeset
for help on using the changeset viewer.