September 2009 - armedbear-devel - mailman3.common-lisp.net

[armedbear-devel] JSR-223: Return immutable lists in ScriptEngineFactory
by Clemens Blamauer 20 Sep '09

20 Sep '09

Hi everyone, I was looking through the JSR-223 code in org.armedbear.lisp.scripting as I noticed that AbclScriptEngineFactory is not fully compliant to JSR-223 [1]. For the methods: - java.util.List<java.lang.String> getExtensions() - java.util.List<java.lang.String> getMimeTypes() - java.util.List<java.lang.String> getNames() _immutable_ Lists should be returned. Please find a remedying patch below. Cheerz, Clemens [1] http://jcp.org/en/jsr/detail?id=223 ---- Index: AbclScriptEngineFactory.java =================================================================== --- AbclScriptEngineFactory.java (revision 12157) +++ AbclScriptEngineFactory.java (working copy) @@ -21,6 +21,7 @@ package org.armedbear.lisp.scripting; import java.util.ArrayList; +import java.util.Collections; import java.util.List; import javax.script.ScriptEngine; @@ -44,7 +45,7 @@ public List<String> getExtensions() { List<String> extensions = new ArrayList<String>(1); extensions.add("lisp"); - return extensions; + return Collections.unmodifiableList(extensions); } @Override @@ -89,7 +90,7 @@ @Override public List<String> getMimeTypes() { - return new ArrayList<String>(); + return Collections.unmodifiableList(new ArrayList<String>()); } @Override @@ -99,7 +100,7 @@ names.add("cl"); names.add("Lisp"); names.add("Common Lisp"); - return names; + return Collections.unmodifiableList(names); } @Override

1 0

[armedbear-devel] Build problem
by Paul 20 Sep '09

20 Sep '09

Can anybody help with this build problem? I'm on MACOSX 10.5.8 trying to build from SVN, which I updated a few minutes ago. Buildfile: build.xml abcl.copy.lisp: [copy] Copying 171 files to /Users/pdo/Lisp/ABCL/build/classes abcl.init: [echo] java.version: 1.5.0_19 [echo] Implementation-Source: ${version.src} abcl.java.warning: abcl.jsr-223.notice: [echo] [echo] Notice: JSR-223 support won't be built since it is not [echo] supported, neither natively by your JVM nor by [echo] libraries in the CLASSPATH. [echo] abcl.compile.java: [javac] Compiling 268 source files to /Users/pdo/Lisp/ABCL/build/ classes abcl.fasls.uptodate: abcl.compile.lisp: [java] Armed Bear Common Lisp 0.15.0 [java] Java 1.5.0_19 Apple Inc. [java] Java HotSpot(TM) Client VM [java] Low-level initialization completed in 1.627 seconds. [java] Startup completed in 7.773 seconds. [java] [java] Caught SIMPLE-ERROR while processing --eval option "(compile-system :zip nil :quit t)": [java] *LISP-HOME* is NIL or invalid. [java] Please set *LISP-HOME* to the full pathname of the directory containing the Lisp system files. BUILD FAILED /Users/pdo/Lisp/ABCL/build.xml:211: Java returned: 2 Thanks, Paul

2 2

[armedbear-devel] [PATCH] Add SYS::*INVOKE-DEBUGGER-HOOK*
by Tobias C. Rittweiler 20 Sep '09

20 Sep '09

The first patch adds SYS::*INVOKE-DEBUGGER-HOOK* which is like *DEBUGGER-HOOK* but is observed by INVOKE-DEBUGGER even when BREAK is called. This obliterates the need to redefine SYS::BREAK in swank-abcl.lisp. A patch for swank-abcl is also attached. -T.

2 1

[armedbear-devel] r12147
by Ville Voutilainen 17 Sep '09

17 Sep '09

Thanks to Douglas Miles, I committed a fix to PRINT-LENGTH.INIT.1 ansi test. I'll commit the rest of Douglas' fixes shortly. Douglas, thanks for the contributions!

1 0

Re: [armedbear-devel] [j-devel] slime swank-abcl.lisp
by Mark Evenson 17 Sep '09

17 Sep '09

On 9/12/09 7:45 AM, Alan Ruttenberg wrote: > Here's a patch against the current swank-abcl.lisp to make a couple of > things work for the trunk abcl. > > I don't want to check it in, as I don't know whether there are issues > with it working for older versions of abcl. > > The fixes make edit definition work, and arglists for generic functions. > > Is there anyone out there who is currently active on slime development > that is comfortable checking these in? Applied to SLIME CVS HEAD. Thanks for the patch! I tested with abcl-0.{15,16} and HEAD with the patch working as I expected. Keeping compatibility with more ancient versions of ABCL takes a too much of my scant resources, but if someone is stuck with a previous version of ABCL they wish to maintain compatibility with SLIME CVS HEAD, drop me an email to work something out. For those following the "old" armedbear-j-devel(a)lists.sourceforge.net list, and perhaps wondering why things have been so quiet lately, note that we moved [ABCL specific traffic to common-lisp.net][1] some months ago. [1]: http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."

2 4

[armedbear-devel] [ANN] Snow 0.1 released - GUI library for ABCL
by Alessio Stalla 15 Sep '09

15 Sep '09

Greetings everyone, I am pleased to announce the first public release of my "Snow" library, available at http://alessiostalla.altervista.org/software/snow/index.php It is a declarative DSL for creating GUIs (Swing-only for now) built on ABCL 0.16. It supports Cells by Ken Tilton and MiG Layout (a declarative, CSS-like layout manager for Swing and SWT). As a bonus, Snow includes the GUI versions of ABCL's inspector, debugger and REPL. Snow is to be considered alpha quality. In particular, % of Swing supported is ridiculously small, and little testing has been performed. If you feel brave enough to play with it, let me know about your experience. Cheers, Alessio

2 3

[armedbear-devel] [from abcl-dev] Question on ABCL-SCRIPT
by Mark Evenson 15 Sep '09

15 Sep '09

Over on the abcl-dev blog OMouse said... I have a question: how do you change the eval/load-script stuff so it doesn't use the ABCL-SCRIPT package? I'm trying to add extensive scripting to a game but I'd like to be able to switch the package so that the scripter can use a huge bunch of variables without me having to :export them. Can anyone help with this question? I must sheepishly confess to not having much experience with ABCL-SCRIPT yet, but the question seems to ask for refinements in our implementation. Posting a reply on the [abcl-dev blog][1] would be great. [1]: http://abcl-dev.blogspot.com/2009/09/abcl-0160-released.html#comments -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."

2 1

[armedbear-devel] Loading ABCL fasls from JARs
by Erik Huelsmann 14 Sep '09

14 Sep '09

Hi Mark, Today I was thinking about what to write in our bi-weekly blog. Then I remembered you committed the support for loading FASLs from JARs. Would you -or someone else- want to write a blog entry on the ABCL-DEV blog to make this feature world-known? Of course, if you don't have time, that's fine too. It's just that I suddenly figured it would be a nice subject to blog about. Bye, Erik.

2 1

[armedbear-devel] asdf regression
by Alan Ruttenberg 11 Sep '09

11 Sep '09

asdf::oos used to take a :verbose argument. It no longer does. This breaks some of my code (I'm trying to migrate to the latest abcl so I can test/use the jar file feature - thanks Mark!) (I've worked around it for now) -Alan

3 10

[armedbear-devel] Summarizing "In-memory compilation status"
by Erik Huelsmann 09 Sep '09

09 Sep '09

As pointed out, Alessio added some primitives required to add in-memory compilation. However, the rest of the thread seems to mix a number of issues and their progress. As a result, I thought a summary might be in order. There were several things "in-memory" versus "using files": 1. Compilation of functions in our JSR-223 support (Alessio changed ABCL's behaviour here) 2. Compilation of lisp forms into compiled functions 3. Compilation of lisp files into fasls With respect to (1): This is where Alessio changed ABCL's behaviour to use COMPILE instead of COMPILE-FILE, eliminating the use of a single temporary file. With respect to (2): Currently, ABCL uses a temporary file for each "compiland" (FLET/LABELS defined function, LAMBDA, DEFUN) in the forms to be compiled. This file is created with a ".cls" extention. After it's written, it gets loaded into the running jvm by loading the bytes in a byte array. That byte array is then resolved to a class. ABCL uses its own class loader to do so. Because the the bytes get written and read without this being required by the Java class loader, there should not be a need to write the bytes out to a file. After the file has been read into memory, the temporary file gets deleted. With respect to (3): Each "compiland" in a file to be compiled leads to a ".cls" file, which is created as a temp file, then read into memory and after that written into the ".abcl" file - which as noted is in fact a .zip file. The intermediate temp file is then deleted. This process too takes much more I/O (what if you're compiling to a network drive with this kind of I/O?!) then required. It's with respect to items (2) and (3) that I'd like to see things changed. In case of (2) there's no reason to send output to any type of disc, while in case (3) it would be beneficial to write our output straight into the ZIP file, instead of using intermediary files. I'm looking for a good solution to both cases. One of the things I came up with is some kind of "storage factory" which would be a function to be called which either generates a stream sending output to the ZIP, or an in-memory stream or a file-backed stream if that's still required. So, what are your comments to that? Bye, Erik.

3 2