armedbear-devel November 2010

armedbear-devel@common-lisp.net

12 participants
33 discussions

[armedbear-devel] directory doesn't honor :wild-inferiors (#P"**/*.*")
by pjb＠informatimago.com 07 Nov '10

07 Nov '10

[pjb@kuiper :0.0 lisp]$ abcl Armed Bear Common Lisp 0.20.0 Java 1.6.0_22 Sun Microsystems Inc. Java HotSpot(TM) Server VM Low-level initialization completed in 0.266 seconds. Startup completed in 0.75 seconds. Type ":help" for a list of available commands. [1] CL-USER(9): (directory "*/*.asd") (#P"/home/pjb/src/git/public/lisp/tools/com.informatimago.common-lisp.tools.make-depends.asd" #P"/home/pjb/src/git/public/lisp/common-lisp/com.informatimago.common-lisp.asd" ...) [1] CL-USER(10): (directory #P"**/*.asd") NIL [1] CL-USER(11): -- __Pascal Bourguignon__ http://www.informatimago.com/ A bad day in () is better than a good day in {}.

3 2

[armedbear-devel] Working toward the 0.23 release
by Erik Huelsmann 06 Nov '10

06 Nov '10

We've had a productive number of weeks since our last release. Changes include: * Running the Maxima test suite without failure [Thanks to the Maxima team for their part in this!] * CLOS thread safety fixes * Fixes to be able to run on Oracle JRockit JVM * Numerous tickets fixed * A new class file writer to build further optimizations upon So, I think we should be moving toward a release real soon now. Is there more to be added to trunk? If not, I'll be branching by the end of the weekend; otherwise, let's discuss and see what timelines to set. Everybody, thanks again for your contributions! Bye, Erik.

2 2

[armedbear-devel] Soliciting (updates to) testimonials
by Erik Huelsmann 04 Nov '10

04 Nov '10

In the interest of informing potential users about the various uses, strengths and weaknesses of ABCL, we have a Testimonials page. However, most of the testimonials don't have a date. That's rather unfortunate, because it makes it hard to judge how valid they still are: over the past three years, we had quite a bit of change in our code base. Most of the changes were driven by CLHS compliance, correctness or code cleanup (to support future maintenance). So, there's a good chance some of the older testimonials don't actually apply to current ABCL versions anymore. Just removing those older testimonials (leaving a blank page) isn't really an option for me. OTOH, leaving them up there without a date isn't really indicative of today's ABCL either. That's why I'm asking you to submit your (updated) testimonials. If you're currently using ABCL (or have been using until recently), but there's no testimonial up on the page from you, please take a quick look at the top testimonial at http://common-lisp.net/project/armedbear/testimonials.shtml (the one by David Kirkman). As you see, it doesn't have to be much, so, creating a testimonial doesn't have to take a lot of time. Taking the half hour to create a testimonial is your opportunity to donate back to the ABCL community! Thanks for your time and contributions, Erik.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-devel November 2010