armedbear-devel

armedbear-devel@common-lisp.net

1199 discussions

[armedbear-devel] Change the default action of 'build.xml' to 'abcl.clean abcl.wrapper'?
by Mark Evenson 26 Oct '09

26 Oct '09

[Including armedbear-devel@ for potential wider dicussion.] On 10/26/09 1:05 PM, Erik Huelsmann wrote: […] > > BTW: I'm always doing complete builds; are you too? Yeah, in fact I think the much more common use case of the build system is 'ant abcl.clean abcl.wrapper'. I almost always want a full build from scratch, which is now taking slightly under two minutes for my MacBook Pro laptop. A couple years ago, a full build took something like five minutes from what I remember, so there was more of a need for incremental builds. What's your usage pattern like? Maybe I should make 'abcl.clean abcl.wrapper' the default target, where the old behavior could be re-restablished via setting an Ant property. This is contrary to the behavior of most build systems that I have experienced, but since we could write a banner message like "Starting build from scratch; set 'abcl.build.incremental' in 'build.properties' to enable incremental builds in the future." Thoughts? -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."

2 1

[armedbear-devel] Binary FASL support
by Erik Huelsmann 26 Oct '09

26 Oct '09

As the result of an attempt to reduce our startup time, I implemented binary FASL support: a compiled lisp function (= Java class) which gets executed instead of the interpreted forms which used to constitute the texty fasl format. The texty format is still there, but in case of a binary fasl only contains 2 forms to be evaluated, the rest will be in the compiled function. I don't feel like we achieved much: my startup times used to be 0.4 s and 1.6 s and that doesn't seem to have changed. Bummer. However, that's probably to be expected, because I was just guessing where our performance issue would be: I want to know how much of the 0.4 and 1.6 seconds are actually spent waiting on I/O happening. In case we're waiting big time on the data coming from the JAR, maybe there's an optimization possible to the way we create/read the JAR file. Any help on the subject of reducing our startup time would be most welcome! Bye, Erik.

2 1

[armedbear-devel] Error in 'test.lisp' to create .abcl_completions
by John Pallister 23 Oct '09

23 Oct '09

Hello list, I think there's an error in the 'test.lisp' code used to create .abcl_completions at http://common-lisp.net/project/armedbear/doc/abcl-install-with-java.html . Basically it should start with (defvar symbols nil) or somesuch to avoid an UNBOUND-VARIABLE error. Cheers, John :^P -- John Pallister john(a)johnp.net john(a)synchromesh.com

2 1

[armedbear-devel] Binary release 0.17 (steps to be taken)
by Erik Huelsmann 23 Oct '09

23 Oct '09

I'm hoping to be able to publish binaries when releasing 0.17. However, I think we're not yet completely ready to do so. We're missing: * Usage descriptions in terms of an INSTALL file, or something similar * Build targets, like we have for the src archives, for abcl-bin-<version>.zip and abcl-bin-<version>.tar.gz * Anything else? As for the archives, I'd like them to contain many of our top-level files (COPYING, README, etc) and instead of the subdirectories, I think it should contain abcl.jar Comments? Bye, Erik.

2 2

[armedbear-devel] Bug: Attempt to GO to a tag whose extent has ended quits ABCL
by Brian Mastenbrook 23 Oct '09

23 Oct '09

When attempting to GO to a tag whose dynamic extent has ended, ABCL quits and prints the name of the exception used for internally handling GO (org.armedbear.lisp.Go). I see the same behavior in compiled or interpreted code. CL-USER(1): (lisp-implementation-version) "0.16.0" CL-USER(2): (let ((f nil)) (tagbody (setf f (lambda () (go foo))) foo) (funcall f)) org.armedbear.lisp.Go abcl-src-0.16.0 chandler$ -- Brian Mastenbrook brian(a)mastenbrook.net http://brian.mastenbrook.net/

2 1

Re: [armedbear-devel] Using Java Libraries
by Carlos Ungil 22 Oct '09

22 Oct '09

> Hi folks, > > I'm searching for a (more systematic) documentation (or tutorial) > about how to use Java libraries from ABCL. > > I couldn't find anything else except the examples on > "http://trac.common-lisp.net/armedbear/browser/trunk/abcl/examples/abcl". > > Is there any such tutorial (or documentation) at all? > Any feedback is very much appreciated! > > Regards > Nik Hello, you might want to check jfli-abcl. Jfli, by Rich Hickey (who would later create Clojure), makes it possible to call Java from LispWorks. It was ported to ABCL by Andras Simon. You can I've just noticed you can find a recent (and improved) copy of jfli-abcl (including sample code) from http://github.com/avodonosov/abcl-idea/tree/master/src/abclidea/lisp/jfli-a… My version of the file has a couple of extra things that might be useful. 1) I had to add a case to infer-box-type to be able to call functions with java.lang.Float arguments. (defun infer-box-type (x) (cond ((null x) nil) ((boxed? x) (jobject-class (get-ref x))) ((integerp x) integer.type) ((typep x 'single-float) float.type) ((numberp x) double.type) ........ 2) I think the following change was done by Alex Mizrahi (I took the file from abcl-web). I don't know if it's still required. < `(defclass ,(class-symbol full-class-name) < ,supers ())))))))) --- > `(unless (get ,class-sym :ensured) ;no fwd ref'd classes in abcl > (ensure-java-class ,full-class-name) > (defclass ,(class-symbol full-class-name) > ,supers ()))))))))) I also added a "doto" macro similar to the one in Clojure (http://clojure.org/java_interop#toc15) (defmacro doto (object &body body) `(let ((object ,object)) ,@(loop for form in body collect `(,(first form) object ,@(rest form))) object)) so I can do things like (document.add (doto (pdfptable.new 3) (pdfptable.addCell (doto (pdfpcell.new (paragraph.new "header with colspan 2")) (pdfpcell.setColspan 2))) (pdfptable.addCell "A") (pdfptable.addCell "B"))) Cheers, Carlos

1 0

[armedbear-devel] Optimizing startup time
by Erik Huelsmann 21 Oct '09

21 Oct '09

Yesterday, Alex Muscar and I were chatting about the options and possibilities to use ABCL on GAE. It turns out that ABCL's startup gets triggered more often than we expected: instances of ABCL may get swapped out of memory or mapped to different servers, meaning ABCL needs to load all from scratch. So, we were evaluating what options we have to optimize ABCL's startup time. As always, I want to base such a decision on facts, so I ran the profiler on ABCL's startup yesterday. The conclusion is that ~ 40 to 45% of our startup time is spent in "privateGetDeclaredConstructors()". This is due to loadCompiledFunction calling the class's newInstance() method. That however, is the processing time spent. I'd love to be able to reduce it, but the function body delegates to a C/C++ function which means I can't fully understand its performance characteristics. Now, the other thing might be "I/O waiting time". Although the profiler measures "run time" and "wait time", I'm not sure how to deduce I/O wait time from that, or how to profile I/O times in another way. If there is considerable I/O wait time, we could probably speed up ABCL's startup process without having to drastically change any design decisions. Does anybody have any comments to that? Helpful remarks on how to find out about I/O wait time? Bye, Erik.

1 0

Re: [armedbear-devel] Using named classes for primitives
by Erik Huelsmann 21 Oct '09

21 Oct '09

On Mon, Oct 19, 2009 at 2:59 PM, Alessio Stalla <alessiostalla(a)gmail.com> wrote: > On Mon, Oct 19, 2009 at 2:22 PM, Alex Muscar <muscar(a)gmail.com> wrote: >> Hi, >> >> I've been messing around with the code. I've managed to load the fasl, >> but I think we're missing some initializations because I get the >> following error: >> >> ERROR placeholder called with arguments: >> #<UNDEFINED-FUNCTION SYSTEM::ENSURE-AVAILABLE-SYMBOLS {E5F46E}> >> >> Here's a full stack trace: >> >> org.armedbear.lisp.ConditionThrowable: java.lang.Error >> at org.armedbear.lisp.Primitives$70.execute(Primitives.java:1459) > > OT, but not too much: if we used named classes for primitives we could > get more meaningful stack traces (say, JCALL instead of > Primitives$XY). I.e. instead of > > private static final Primitive xyz = new Primitive(...) { ... }; > > we could use > > private static class JCALL extends Primitive { > JCALL(...) { super(...); } > ... > } > private static final Primitive xyz = new JCALL(...); > > a bit more verbose, but worth the effort imho. I think so too. However, there are a few too many of these to start changing them over now. Or does anybody feel like hacking up a perl script to get it done? :-) Bye, Erik.

4 7

[armedbear-devel] abcl on AppEngine
by Alex Muscar 19 Oct '09

19 Oct '09

Here's the first abcl "app" running on Google AppEngine: http://1.latest.abcl-test.appspot.com/hello . It's not much, but it's a start ;). -- All the best, Alex Muscar

1 0

[armedbear-devel] Using Java Libraries
by nitralime 19 Oct '09

19 Oct '09

Hi folks, I'm searching for a (more systematic) documentation (or tutorial) about how to use Java libraries from ABCL. I couldn't find anything else except the examples on "http://trac.common-lisp.net/armedbear/browser/trunk/abcl/examples/abcl". Is there any such tutorial (or documentation) at all? Any feedback is very much appreciated! Regards Nik

3 5

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-devel