armedbear-devel August 2009

armedbear-devel@common-lisp.net

14 participants
16 discussions

Re: [armedbear-devel] progress on Maxima + ABCL -- light at the end of the tunnel!
by Erik Huelsmann 09 Aug '09

09 Aug '09

On Thu, Jul 30, 2009 at 8:04 PM, Robert Dodier<robert_dodier(a)yahoo.com> wrote: > > --- On Thu, 7/30/09, Erik Huelsmann <ehuels(a)gmail.com> wrote: > >> Another question: I'm running these profiles too, of >> course. On my system rtest_integrate takes forever to run, >> could that be this is the main cause it takes that long? >> Should we start profiling only that test set? > > Yes, that sounds reasonable. The integration code makes > use of the sign-inference code, to which DGR and DLS belong, > so maybe it is actually true that they are doing something > that is taking a long time. Well, I found a reason why ABCL may be taking so extremely long: in SPRDET.lisp, there's a top-level special declaration of the variable name X. In ABCL such declarations are retained after file compilation completes (which is allowed by the spec). Hence, after compilation of sprdet.lisp, any reference to a variable with the name X, or creation of a binding thereof, is a special binding. In ABCL, there's a non-trivial difference between evaluation of a special variable versus a local variable. So, renaming the special variable could be a solution, but that would require a change on part of Maxima; I'm thinking about how to revert the side effect at the end of the file compilation. That's a non-trivial change to ABCL. I haven't figured it out yet. Bye, Erik.

2 5

[armedbear-devel] European Common Lisp Meeting
by Arthur Lemmens 07 Aug '09

07 Aug '09

Hi, We just want to remind you that the registration deadline for this year's ECLM (European Common Lisp Meeting) is August 15. You can still register at http://weitz.de/eclm2009 We hope to see you in Hamburg, Edi Weitz & Arthur Lemmens

1 0

[armedbear-devel] [PATCH] Problems with new JavaObject.javaInstance(Class c) and JSS
by Mark Evenson 05 Aug '09

05 Aug '09

Unfortunately Alessio's (and Tobias?) work on [adding richness to inspection of Java objects][1] contains a bug that manifests itself in stopping [JSS][2] from working. The attached patch gets JSS to run again, but I am not sure the right way to fix the problem in the trunk, mainly as I don't understand all of our conversion rules, and how they interact with Java's autoboxing. The problem with JSS occurs when JavaObject.javaInstance(Class c) is invoked with a Class from a primitive boolean on an JavaObject that wraps a java.lang.Boolean. The call to java.lang.Class.isAssignableFrom() has an oddly (to me) specific contract that "[i]if [the] Class object represents a primitive type, this method returns true if the specified Class parameter is exactly this Class object; otherwise it returns false." This makes JavaObject<java.lang.Boolean>.javaInstance(boolean) fail, when everything seems to work fine if we simply return the wrapped object. What I don't understand mainly is if boolean/java.lang.Boolean objects are somehow special in our treatment of them, or should we do this for all of the other primitive types? [1]: http://trac.common-lisp.net/armedbear/changeset/12081 [2]: http://mumble.net:8080/svn/lsw/trunk/jss/ -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."

3 5

[armedbear-devel] test, please ignore
by Anton Vodonosov 02 Aug '09

02 Aug '09

1 0

[armedbear-devel] [PATCH] 20090731b Java stack frames
by Mark Evenson 01 Aug '09

01 Aug '09

Last night I sent out an older version of my work; attached is the correct current version. Mark -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."

1 0

[armedbear-devel] Integration of CL and Java
by Tobias C. Rittweiler 01 Aug '09

01 Aug '09

To incite some discussion about what steps are required to make it convenient to write Java from within CL. The result should probably be added to Trac. Short term: * make Java objects inspectable. * make DESCRIBE be useful on Java objects. Should mention inheritance tree, public attributes, and methods. * fix inconsistencies, for example JMETHOD takes class-name first, then method-name, but JSTATIC takes it the other way around. Medium term: * make JMethods be a subclass of FUNCALLABLE-INSTANCE, so they can be funcalled, passed to HOFs, stored into SYMBOL-FUNCTION etc. * add reader-macros for convenience. For example, #J'class.method for (jmethod "class" "method"). * add iteration macro, HOFs, for Java Collections. * Figure out how to get arglist information from Java methods. * Documentation * Useful PRINT-OBJECT methods for Java Objects. For example, Collection objects could be printed showing their content, e.g. #<JAVA-CLASS COLLECTION [a b c d e]>. Make sure to make it heed the printer variables properly, though. Long term: * Add an extensible sequence protocol, and make Java Collection abide it. * integrate Java's object hierarchy into the CLOS object hierarchy. I'm not a CLOS expert, but a few people come to mind who to ask. * Make it possible to extend Java classes from Lisp. * Make it possible to implement Java interfaces from Lisp. People who have experience with Clojure, and other Lisp-like languages on the JVM are welcomed to chime in how other do the integration, and how they like it. Also people who have opinions how they'd like it to look like. -T.

4 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-devel August 2009