[armedbear-cvs] r13483 - public_html
mevenson at common-lisp.net
mevenson at common-lisp.net
Sat Aug 13 06:46:16 UTC 2011
Author: mevenson
Date: Fri Aug 12 23:46:15 2011
New Revision: 13483
Log:
FAQ improvements.
Explain how to avoid recompilation.
Remove claim that Gray streams are broken due to improvements made to
get Huchentoot working.
Rephrase the issue reporting procedure, note #abcl as a resource.
State goal for Quicklisp compatiblity.
Update failing test number for abcl-0.26.1.
Mention HTTP SVN repository.
Modified:
public_html/faq.shtml
Modified: public_html/faq.shtml
==============================================================================
--- public_html/faq.shtml Fri Aug 12 22:48:48 2011 (r13482)
+++ public_html/faq.shtml Fri Aug 12 23:46:15 2011 (r13483)
@@ -29,6 +29,13 @@
<li><a href="#documentation">Where is ABCL's documentation?</a></li>
</ol>
</li> <!-- general -->
+
+ <li><a href="#building">Building</a>
+ <ol>
+ <li><a href="#avoiding-recompilation">The Ant build process seems to recompile from scratch each time. How do I avoid this?</a></li>
+ </ol>
+ </li>
+
</ol>
@@ -41,15 +48,13 @@
the exception of the implementation of the long form of
DEFINE-METHOD-COMBINATION.</p>
-<p>Unfortunately, the CLOS implementation is not accessible through
-a MOP (MetaObject Protocol). Any contributions in this area would
-be greatly appreciated, ofcourse.</p>
-
-<p>One thing which is considered almost standard lisp - because all
-implementations deliver it - is "Gray streams". Unfortunately ABCLs
-version is broken [as per 05/2009]. It should be noted this is by no
-means the final state of affairs, though, merely a warning that one
-can't depend on this feature at the moment.</p>
+<p>
+Unfortunately, the CLOS implementation is not fully completely through
+a MOP (MetaObject Protocol). Perhaps roughly a third of the
+functionality defined by <a
+href="http://www.lisp.org/mop/index.html">AMOP</a> is present. Any
+contributions in this area would be greatly appreciated, of course.
+</p>
</div>
@@ -69,13 +74,13 @@
In general, such usage means that whenever you keep ABCL as a separate
jar file, you won't have licensing problems. The combining in the
Classpath exception means that you can
-
+</p>
<ol>
<li>Extend ABCL java classes in your program</li>
<li>Use ABCL java classes in your program</li>
<li>Invoke ABCL lisp functions in your program</li>
</ol>
-
+<p>
without having to worry about the licensing. You do have to
distribute the source code of ABCL (including modifications)
if you distribute ABCL, but otherwise the license of ABCL is not viral.
@@ -86,16 +91,30 @@
<div class="h3" title="bug-reporting" id="bug-reporting">
<h3>How/Where should I report bugs?</h3>
-<p>There is a list of currently known problems (bugs) in our
-<a href="http://trac.common-lisp.net/armedbear/report/1">bug tracker</a>.
-Unfortunately, due to spamming problems, administration of bugs has been
-closed for anybody but common-lisp.net members.</p>
-
-<p>If you found a bug which is not on the list, or you want to stress
-the importance of one that is, please mail our <a
-href="http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel">mailing list</a> about it.</p>
-</div>
+<p>
+
+The current state of issues can be found in the <a
+href="http://trac.common-lisp.net/armedbear/report/1">ABCL issue
+tracker</a>. Unfortunately, due to spamming problems, administration
+of bugs has been closed for anybody but common-lisp.net members.</p>
+
+<p>
+To report a bug, please mail a description of the problem, the version
+of ABCL you are using, and if possible a set of steps to reproduce the
+problem to the <a
+href="http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel">armedbear-devel
+mailing list</a>. We try to respond within a day at most to messages.
+A convenient way to browse the mailing list archives can be found by
+<a href="http://news.gmane.org/gmane.lisp.armedbear.devel">the gmane
+loom interface to the NNTP group gmane.lisp.armedbear.devel</a>.
+</p>
+
+<p>
+Developers can also usually be found on the <a
+href="http://webchat.freenode.net/?randomnick=1&channels=abcl&prompt=1&uio=d4">#abcl
+irc channel</a>.
+</p>
<div class="h3" title="speed" id="speed">
<h3>Is ABCL faster or slower than implementation XYZ?</h3>
@@ -133,8 +152,11 @@
to run existing Lisp code</li>
</ol>
-<p>The plan is to add to the list above software from Edi Weitz, who
- wrote some great libraries.</p>
+<p>
+The plan is to ensure that ABCL runs with the software provided by
+<a href="http://www.quicklisp.org/">Quicklisp</a>. For many packages available from Quicklisp,
+this is already the case.
+</p>
<p>The first item is being measured by running the ANSI test suite compliance
tests. The second item is measured by compiling and running the test suite
@@ -142,9 +164,10 @@
Additionally, compilation of <a href="http://ap5.com/">AP5</a> is used to
improve this measure too.</p>
-<p>ABCL 0.23.0 fails 31 out of 21702 tests in the ANSI test suite
- in interpreted and compiled modes, a constant number over the past
- releases. Most failures relate to pretty printing.</p>
+<p>ABCL 0.26.1 fails roughly 20 out of 21702 tests in the ANSI test
+suite in interpreted and compiled modes, a constant number over the
+past releases. Most failures relate to pretty printing.</p>
+
<p>As a measure of 'improvement achieved', the development team refers
to the number of failing tests in the Maxima test suite too.
ABCL 0.23.0 is able to run the test suite without failures, coming from
@@ -160,6 +183,12 @@
you can check out through
svn://common-lisp.net/project/armedbear/svn/trunk/abcl.</p>
+<p>
+This repository is also exported read-only via HTTP at
+<a href="http://svn.common-lisp.net/armedbear/trunk/abcl">http://svn.common-lisp.net/armedbear/trunk/abcl</a>
+</p>
+
+
</div>
<div class="h3" title="documentation" id="documentation">
@@ -177,8 +206,26 @@
</ol>
</div>
+</div>
+
+<div class="h2" title="Building" id="building">
+<h2>Building</h2>
+
+<div class="h3" title="Avoiding recompilation" id="avoiding-recompilation">
+<h3>The Ant build process seems to recompile from scratch each time. How do I avoid this?</h3>
+
+<p>
+If the JVM system property <code>abcl.build.incremental</code> is set,
+the Ant build process will attempt to build ABCL incrementally
+by not removing any intermediate results. The easiest way to enable
+this property is to copy the 'abcl.properties.in' file to
+'abcl.properties', then uncomment the line referencing the setting of
+the <code>abcl.build.incremental</code> property.
+</p>
</div>
+</div>
+</div>
<div style="float:left;width:100%">
<hr />
More information about the armedbear-cvs
mailing list