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

[Armedbear-devel] loading Maxima via ASDF
by Robert Dodier 15 May '14

15 May '14

After some flailing around, I managed to figure out how to load Maxima via ASDF + ABCL. For the record, ASDF 3.1.0.103 + ABCL 1.3.1. The problem I reported about ASDF not looking in the right place for the .abcl files might be due to the maxima.asd specifying a place without telling ASDF (?? not sure). By disabling ASDF's output translation stuff, the problem went away. Alternatively, one could nuke the assignment to ASDF:*BINARY-OUTPUT-DIR* in maxima.asd and let ASDF figure out where to put stuff (somewhere below ~/.cache/ common-lisp, it appears). It appears to be necessary now to specify something for ASDF:*CENTRAL-REPOSITORY*. I hadn't found that necessary before. (Last time I tried might have been a couple of years ago.) So with maxima-5.33.0.tar.gz unpacked, this recipe worked for me: (0) cd maxima-5.33.0/src (1) edit maxima.asd to say binary-abcl instead of binary-ecl for ASDF:*BINARY-OUTPUT-DIR*. (Not strictly necessary.) ASDF thens writes stuff into ./binary-abcl. (2) launch ABCL via: java -jar path/to/abcl.jar (3) in ABCL repl: (require 'asdf) (setf asdf:*central-registry* '(*default-pathname-defaults*)) (asdf:disable-output-translations) (asdf:operate 'asdf:load-op :maxima) (4) launch Maxima interpreter: (cl-user::run) Plotting, help, run_testsuite all work as expected; test suite has a few unexpected errors, mostly numerical. FWIW Robert Dodier _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

1 0

[Armedbear-devel] HEADS-UP: r14694 changes semantics (sometimes) of CL:NIL to Java from JAVA:+NULL+ to JAVA:+FALSE+
by Mark Evenson 15 May '14

15 May '14

With [r14694][], we now convert CL:T and CL:NIL to JAVA:+TRUE+ and JAVA:+FALSE+ respectively when invoking JVM methods through the JAVA package, establishing the "natural" equivalence for boolean truth values. This may break some existing usage in that previously CL:NIL was converted to a Java 'null' reference. Users now need to specify JAVA:+NULL+ explicitly when desiring to pass 'null' Java references as an argument in invoking JVM methods. As far as I can tell from what I can from testing examples of available consumers of the JAVA package, this doesn’t break existing usage, as we have been advising use JAVA:+NULL+ to denote a null reference explicitly since its introduction some three years ago [r13359][]. And until I inspected the underlying JAVA code yesterday, I wasn’t even aware of the conversion of CL:NIL to JAVA:+NULL+. Nevertheless, please speak up if this breaks something for you that you relied upon. Unless I hear otherwise, I am going to back port this change to abcl-1.3.1 as the last change before a release. While strictly speaking from a release engineering perspective, this sort of change should wait until a major revision release, I am planning on using abcl-1.3.1 in production next week with [lsw2][], which sort of relies on this behavior. I beg the ABCL community’s indulgence in this deviation from release engineering best practices, unless somebody speaks up soon that this is a very bad idea. This change implements the requests in [ticket-84][] and [ticket-339][]. [ticket-84]: http://abcl.org/trac/ticket/84> [ticket-339]: http://abcl.org/trac/ticket/339 [r14694]: http://abcl.org/trac/changeset/14694 [r13359]: http://abcl.org/trac/changeset/13359 [lsw2]: https://code.google.com/p/lsw2/ -- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now." _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

1 0

[Armedbear-devel] ABCL on iOS via RoboVM?
by John Pallister 07 May '14

07 May '14

Hello list, I was wondering whether anyone has tried to get ABCL running on iOS by means of RoboVM [1]? I see that people have done this with Clojure [2]. Also, can I ask how the Android build target is coming along? I'm weighing up LambdaNative [3] vs. alternatives for Lisp development on iOS and Android. Cheers, John :^P [1] http://www.robovm.org/ [2] https://github.com/oakes/lein-fruit [3] http://www.lambdanative.org/ -- John Pallister john(a)johnp.net john(a)synchromesh.com _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

1 0

[Armedbear-devel] [CfP] International Lisp Conference 2014, Aug. 14-17, Montreal
by Didier Verna 07 May '14

07 May '14

ILC 2014 - International Lisp Conference "Lisp on the Move" August 14-17 2014, Université de Montréal, Montréal, Canada Sponsored by the Association of Lisp Users In cooperation with: ACM SIGPLAN http://www.international-lisp-conference.org Scope: Lisp is one of the greatest ideas from computer science and a major influence for almost all programming languages and for all sufficiently complex software applications. The International Lisp Conference is a forum for the discussion of Lisp and, in particular, the design, implementation and application of any of the Lisp dialects. We encourage everyone interested in Lisp to participate. We invite high quality submissions in all areas involving Lisp dialects and any other languages in the Lisp family, including, but not limited to, ACL2, AutoLisp, Clojure, Common Lisp, ECMAScript, Dylan, Emacs Lisp, ISLISP, Racket, Scheme, SKILL, HOP etc. The conference proceedings will be published in the ACM Digital Library. This year's focus will be directed towards integrated solutions, including mobile computing. We especially invite submissions in the following areas: * Pervasive computing Interoperability Portability Implementation * challenges/tradeoffs for embedded/mobile platforms Language * support for mobile toolkits and frameworks Language support for * distribution Language support for reliability, availability, and * serviceability Mobile IDEs Mobile applications Contributions are also welcome in other areas, including but not limited to: * Language design and implementation Language integration, * inter-operation and deployment Applications (especially * commercial) Reflection, meta-object protocols, meta-programming * Domain-specific languages Programming paradigms and environments * Efficient parallel and concurrent computation Language support for * managing both manual and automatic GC Theorem proving Scientific * computing Data mining Semantic web Technical Programme: Original submissions in all areas related to the conference themes are invited for the following categories: Papers: Technical papers of up to 10 pages that describe original results. Demonstrations: Abstracts of up to 2 pages for demonstrations of tools, libraries and applications. Workshops: Abstracts of up to 2 pages for groups of people who intend to work on a focused topic for half a day. Tutorials: Abstracts of up to 2 pages for in-depth presentations about topics of special interest for 1 to 2 hours. Panel discussions: Abstracts of up to 2 pages for discussions about current themes. Panel discussion proposals must mention panel member who are willing to partake in a discussion. The conference will also provide slots for lightning talks, to be registered on-site every day. For inquiries about any other kind of participation (commercial exhibits, advertising, prizes, book signing etc.), please see the contacts below. Important Dates: - May 18, 2014: Submission deadline - June 09, 2014: Notification of acceptance - June 29, 2014: Final Papers due - August 14, 2014: Conference All submissions should be formatted following the ACM SIGS guidelines and include ACM classification categories and terms. For more information on the submission guidelines and the ACM keywords, see: http://www.acm.org/sigs/publications/proceedings-templates and http://www.acm.org/about/class/1998. Submissions should be uploaded to Easy Chair, at the following address: https://www.easychair.org/conferences/?conf=ilc14 Organizing Committee: General Chair: Marc Feeley (Université de Montréal, Montréal, Canada) Programme Chair: Didier Verna (EPITA Research lab, Paris, France) Local chair: Marc Feeley (Université de Montréal, Montréal, Canada) Programme Committee: Charlotte Herzeel, IMEC, ExaScience Life Lab, Belgium Damir Cavar, Eastern Michigan University, USA Dave Herman, Mozilla Research, USA Greg Pfeil, Clozure Associates, USA Irène Anne Durand, LaBRI University of Bordeaux, France Jim Newton, Cadence Design Systems, France Kuroda Hisao, Mathematical Systems Inc., Japan Matthew Might, University of Utah, USA Nicolas Neuss, Friedrich Alexander Universitat, Germany Ralf Möller, TUHH, Germany Sam Tobin-Hochstadt, Northeastern University, USA William Byrd, University of Utah, USA Contacts: * General Questions: ilc14-organizing-committee at alu.org * Programme Committee: ilc14 at easychair.org For more information, see http://www.international-lisp-conference.org -- Resistance is futile. You will be jazzimilated. Lisp, Jazz, Aïkido: http://www.didierverna.info _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

1 0

[Armedbear-devel] symbol-macrolet + nth-value
by James M. Lawrence 06 May '14

06 May '14

Hello, (defun foo () (symbol-macrolet ((x 3)) (symbol-macrolet ((y (nth-value 0 x))) y))) Compiling this with COMPILE (C-c-c in slime) warns about X being undefined, and an unbound X error occurs when FOO is run. (macroexpand-1 '(defun foo () (symbol-macrolet ((x 3)) (symbol-macrolet ((y (nth-value 0 x))) y)))) ;;=> (PROG1 (SYSTEM:%DEFUN 'FOO (SYSTEM:NAMED-LAMBDA FOO NIL (BLOCK FOO (LOCALLY (LOCALLY (NTH-VALUE 0 X))))))) X didn't get expanded. There is no problem when compiling the DEFUN form with COMPILE-FILE (C-c-k). _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

1 0

[Asdf-devel] ASDF 3.1.2 released
by Robert P. Goldman 06 May '14

06 May '14

The release version of ASDF 3.1, version 3.1.2, has finally arrived. It is loaded with bug-fixes, more portability (substantially better support on Windows; several new lisp implementations), better documentation (extensive revisions to the Texinfo manual), and new convenience features such as PACKAGE-INFERRED-SYSTEMs. We urge the maintainers of lisp implementations to move to version 3.1.2 directly, as it is clearly superior to its predecessors. This is especially true if you are currently bundling a pre-release version of ASDF. For a list of changes, see the attached changelog. Special thanks to Dave Cooper and Anton Vodonosov (alphabetically) for testing support. Thanks to all those who have participated in the discussions on ASDF-devel for bug fixes, suggestions, and course corrections. Thanks to Pete Keller for proofreading this announcement; any remaining errors are mine alone. Although he is no longer the lead maintainer, François-René Rideau (Fare), has continued to expend vast amounts of effort on ASDF, and provided invaluable guidance to the code submitted by the rest of us. The latest version of ASDF is available at the project website: http://common-lisp.net/project/asdf/ Robert P. Goldman ASDF maintainer-in-chief _______________________________________________ Asdf-devel mailing list Asdf-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel

1 0

[Armedbear-devel] ABCL 1.3.1 testgrid results - no regressions
by Anton Vodonosov 01 May '14

01 May '14

Hi, I have tested ABCL 1.3.1, no regressions comparing to 1.3.0 and 1.2.1: http://common-lisp.net/project/cl-test-grid/abcl/abcl-diff23.html http://common-lisp.net/project/cl-test-grid/abcl/abcl-diff24.html _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

1 0

[Armedbear-devel] Fixing #352 / JSS fails to introspect foo(long) methods
by olof＠macrolet.net 17 Apr '14

17 Apr '14

Hi, I've been trying to improve my idea in [1]. Attached is a slightly different patch, still with the same general idea though. I've added two tests, however I'd still like to do a bit more than that, especially testing the correct resolution of methods, i.e. Java::isMoreSpecialized. My current understanding is that with this patch all possible methods (like for the attached class DummyMethods) are found, but that isMoreSpecialized doesn't actually do what its name implies, namely finding the most specialized method. That is, I'm assuming that JCALL is supposed to use the (exact) same kind of method resolution as Java (if no method signature is given)? Additionally I actually wanted to add DummyMethods for testing from java-tests.lisp, but didn't work out for now. Best regards, Olof [1]: http://abcl.org/trac/ticket/352 _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

2 2

[Armedbear-devel] PROBE-DIRECTORY borks on wildcard character
by Faré 15 Apr '14

15 Apr '14

EXTENSIONS:PROBE-DIRECTORY fails when the directory name has wildcard characters See: https://bugs.launchpad.net/asdf/+bug/1307571 —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Meta is Better. Anything you can do, I can do Meta. — Patrick Logan _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

2 1

[armedbear-devel] ASDF-JAR vs ASDF3 deployment support
by Erik Huelsmann 04 Apr '13

04 Apr '13

Hi all, Some years ago, Mark wrote ASDF-JAR; a solution to package ASDF systems and their dependencies in JARs. As it turns out, the solution chosen has some problems with correctly packaging ASDs for systems which use the #. reader macro. As an example: bordeaux-threads uses a version.lisp-sexp file to canonically define the version number and the system definition reads that file in a #. form. However, this file isn't packaged because it's not part of the file listing in the system definition. This means asdf can't load the definition after deployment. With the advent of ASDF3, its developers have created infrastructure to combine fasls of a single system and even fasls of a system and all its dependencies into a single large combined FASL. Among others, this new infrastructure does not run into the issue ASDF-JAR is running into. While not completely equivalent to the JAR solution, using this infrastructure would help us a huge step along that way of getting better deployment. My current thinking is that if the single-packed-FASL needs to end up as a jar, we can work on that as a next step. The first step to take would be to create "concatenate fasls" functionality, which would do the following: * Detect all the file entries in all the passed-in fasls * Create a new output zip file with directories for each fasl being packed, populated with the files and directories of that fasl * create a toplevel ._ file which loads the sub-fasls' ._ files Comments? Bye, Erik.

5 8