Ignore:
Timestamp:
08/13/11 06:46:15 (10 years ago)
Author:
Mark Evenson
Message:

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.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • public_html/faq.shtml

    r13073 r13483  
    3030  </ol>
    3131  </li> <!-- general -->
     32
     33  <li><a href="#building">Building</a>
     34  <ol>
     35    <li><a href="#avoiding-recompilation">The Ant build process seems to recompile from scratch each time.  How do I avoid this?</a></li>
     36  </ol>
     37  </li>
     38
    3239</ol>
    3340
     
    4249DEFINE-METHOD-COMBINATION.</p>
    4350
    44 <p>Unfortunately, the CLOS implementation is not accessible through
    45 a MOP (MetaObject Protocol). Any contributions in this area would
    46 be greatly appreciated, ofcourse.</p>
    47 
    48 <p>One thing which is considered almost standard lisp - because all
    49 implementations deliver it - is "Gray streams". Unfortunately ABCLs
    50 version is broken [as per 05/2009]. It should be noted this is by no
    51 means the final state of affairs, though, merely a warning that one
    52 can't depend on this feature at the moment.</p>
     51<p>
     52Unfortunately, the CLOS implementation is not fully completely through
     53a MOP (MetaObject Protocol). Perhaps roughly a third of the
     54functionality defined by <a
     55href="http://www.lisp.org/mop/index.html">AMOP</a> is present.  Any
     56contributions in this area would be greatly appreciated, of course.
     57</p>
    5358
    5459</div>
     
    7075jar file, you won't have licensing problems. The combining in the
    7176Classpath exception means that you can
    72 
     77</p>
    7378<ol>
    7479<li>Extend ABCL java classes in your program</li>
     
    7681<li>Invoke ABCL lisp functions in your program</li>
    7782</ol>
    78 
     83<p>
    7984without having to worry about the licensing. You do have to
    8085distribute the source code of ABCL (including modifications)
     
    8792<h3>How/Where should I report bugs?</h3>
    8893
    89 <p>There is a list of currently known problems (bugs) in our
    90 <a href="http://trac.common-lisp.net/armedbear/report/1">bug tracker</a>.
    91 Unfortunately, due to spamming problems, administration of bugs has been
    92 closed for anybody but common-lisp.net members.</p>
    93 
    94 <p>If you found a bug which is not on the list, or you want to stress
    95 the importance of one that is, please mail our <a
    96 href="http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel">mailing list</a> about it.</p>
    97 </div>
    98 
     94<p>
     95
     96The current state of issues can be found in the <a
     97href="http://trac.common-lisp.net/armedbear/report/1">ABCL issue
     98tracker</a>.  Unfortunately, due to spamming problems, administration
     99of bugs has been closed for anybody but common-lisp.net members.</p>
     100
     101<p>
     102
     103To report a bug, please mail a description of the problem, the version
     104of ABCL you are using, and if possible a set of steps to reproduce the
     105problem to the <a
     106href="http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel">armedbear-devel
     107mailing list</a>.  We try to respond within a day at most to messages.
     108A convenient way to browse the mailing list archives can be found by
     109<a href="http://news.gmane.org/gmane.lisp.armedbear.devel">the gmane
     110loom interface to the NNTP group gmane.lisp.armedbear.devel</a>.
     111</p>
     112
     113<p>
     114Developers can also usually be found on the <a
     115href="http://webchat.freenode.net/?randomnick=1&channels=abcl&prompt=1&uio=d4">#abcl
     116irc channel</a>.
     117</p>
    99118
    100119<div class="h3" title="speed" id="speed">
     
    134153</ol>
    135154
    136 <p>The plan is to add to the list above software from Edi Weitz, who
    137  wrote some great libraries.</p>
     155<p>
     156The plan is to ensure that ABCL runs with the software provided by
     157<a href="http://www.quicklisp.org/">Quicklisp</a>.  For many packages available from Quicklisp,
     158this is already the case.
     159</p>
    138160
    139161<p>The first item is being measured by running the ANSI test suite compliance
     
    143165  improve this measure too.</p>
    144166
    145 <p>ABCL 0.23.0 fails 31 out of 21702 tests in the ANSI test suite
    146   in interpreted and compiled modes, a constant number over the past
    147   releases.  Most failures relate to pretty printing.</p>
     167<p>ABCL 0.26.1 fails roughly 20 out of 21702 tests in the ANSI test
     168suite in interpreted and compiled modes, a constant number over the
     169past releases.  Most failures relate to pretty printing.</p>
     170
    148171<p>As a measure of 'improvement achieved', the development team refers
    149172  to the number of failing tests in the Maxima test suite too.
     
    160183you can check out through
    161184svn://common-lisp.net/project/armedbear/svn/trunk/abcl.</p>
     185
     186<p>
     187This repository is also exported read-only via HTTP at
     188<a href="http://svn.common-lisp.net/armedbear/trunk/abcl">http://svn.common-lisp.net/armedbear/trunk/abcl</a>
     189</p>
     190
    162191
    163192</div>
     
    178207
    179208</div>
    180 
     209</div>
     210
     211<div class="h2" title="Building" id="building">
     212<h2>Building</h2>
     213
     214<div class="h3" title="Avoiding recompilation" id="avoiding-recompilation">
     215<h3>The Ant build process seems to recompile from scratch each time.  How do I avoid this?</h3>
     216
     217<p>
     218If the JVM system property <code>abcl.build.incremental</code> is set,
     219the Ant build process will attempt to build ABCL incrementally
     220by not removing any intermediate results.  The easiest way to enable
     221this property is to copy the 'abcl.properties.in' file to
     222'abcl.properties', then uncomment the line referencing the setting of
     223the <code>abcl.build.incremental</code> property.
     224</p>
     225
     226</div>
     227</div>
    181228</div>
    182229
Note: See TracChangeset for help on using the changeset viewer.