Changeset 13165
- Timestamp:
- 01/20/11 14:08:23 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/abcl/README
r12900 r13165 46 46 which should result in output like the following 47 47 48 Armed Bear Common Lisp 0. 19.149 Java 1.6.0_ 14Sun Microsystems Inc.48 Armed Bear Common Lisp 0.25.0 49 Java 1.6.0_21 Sun Microsystems Inc. 50 50 Java HotSpot(TM) Client VM 51 Low-level initialization completed in 0. 9seconds.51 Low-level initialization completed in 0.3 seconds. 52 52 Startup completed in 2.294 seconds. 53 53 Type ":help" for a list of available commands. … … 61 61 preferred (and most tested way) is to being to use the Ant build tool: 62 62 63 * Use the Ant build tool for Java environments. 63 * Use the Ant build tool for Java environments. 64 64 65 65 * Use the Netbeans 6.x IDE to open ABCL as a project. … … 72 72 tested). Just the JRE isn't enough, as you need the Java compiler 73 73 ('javac') to compile the Java source of the ABCL implementation. 74 75 When deploying ABCL, the JDK isn't a requirement for the installation 76 site: ABCL compiles directly to byte code, avoiding the need for the 77 'javac' compiler in deployment environments. 74 78 75 79 … … 85 89 Then simply executing 86 90 87 unix$ ant 91 unix$ ant 88 92 89 93 or 90 cmd$ ant.bat 94 cmd$ ant.bat 91 95 92 96 from the directory containing this README file will create an … … 137 141 on Unix to start ABCL. Note that this wrappers contain absolute 138 142 paths, so you'll need to edit them if you move things around after the 139 build. 143 build. 140 144 141 145 If you're developing on ABCL, you may want to use … … 151 155 This invokes javac separately for each .java file, which avoids running 152 156 into limitations on command line length (but is a lot slower). 153 157 154 158 ** Building from another Lisp by hand 155 159 … … 158 162 159 163 CL-USER> (build-abcl:build-abcl :clean t :full t) 160 164 161 165 will build ABCL. If ASDF isn't present, simply LOAD the 162 166 'customizations.lisp' and 'build-abcl.lisp' files to achieve the same … … 169 173 A lot of (renewed) energy has been spent to make ABCL a compliant 170 174 and practically useable Common Lisp implementation. Because of this, 171 ABCL 0.19.1 now fails only 29 out of 21702 tests in the ANSI CL test 172 suite. Next to that, the fail count of the Maxima test suite has been 173 reduced to only 5 - rounding errors. 174 175 ABCL's CLOS does not handle on-the-fly redefinition of classes 176 correctly. Quite a bit of energy has been spent in versions 0.16.0 and 177 0.17.0 to improve CLOS performance. There is no support for the long 178 form of DEFINE-METHOD-COMBINATION, and certain other required CLOS 179 features are also missing. Enough CLOS is there to run 180 ASDF2 and CL-PPCRE. 175 ABCL 0.25.0 now fails only 28 out of 21702 tests in the ANSI CL test 176 suite. In addition, Maxima's test suite runs without failures now 177 and ABCL's CLOS complete, with the exception of the long form of 178 DEFINE-METHOD-COMBINATION - which is an ongoing effort. 181 179 182 180 There is no MOP worth mentioning. 183 181 184 Patches to address any of the issues mentioned above will be gladly185 accepted.182 Patches to address any of the issues mentioned above will 183 be gladly accepted. 186 184 187 185 Please report problems to the development mailing list: … … 193 191 On behalf of all ABCL development team and contributors, 194 192 Erik Huelsmann 195 March 20, 2010 193 January 20, 2011
Note: See TracChangeset
for help on using the changeset viewer.