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

[armedbear-devel] Setup changes for cl-test-grid.cloud.efficito.com
by Erik Huelsmann 08 Apr '15

08 Apr '15

Hi Anton, Looking at some of the test grid failures for ABCL, I noticed some of the OpenGL packages failing due to being unable to locate LibGL.so. To resolve that, I ran: $ aptitude install libgl1-mesa-swx11 Then I noticed something wanted to require JSS, but didn't know how to, so I've added "(require :abcl-contrib)" to /home/testgrid/.abclrc. With these in place cl-glfw-opengl-core seems to load just fine. Any other libraries or measures I should take in order to be able to load (currently failing) systems? Bye, Erik.

3 3

[armedbear-devel] bug in format ~f
by Carlos Ungil 03 Apr '13

03 Apr '13

Hello, comparing output from different implementations I've found the following (minor) bug: > (format t "~,2f" 0.999) 1.0 ;; should be 1.00 I think there is a problem here as well: > (format t "~5f" 0.00000001) .0000 ;; should print " 0.0" Only SBCL gives the output I would expect, most implementations print ".0000" as ABCL does. From the HyperSpec 22.3.3.1: "If the parameter d is omitted, then there is no constraint on the number of digits to appear after the decimal point. A value is chosen for d in such a way that as many digits as possible may be printed subject to the width constraint imposed by the parameter w and the constraint that ___no trailing zero digits may appear in the fraction, except that if the fraction to be printed is zero, then a single zero digit should appear after the decimal point___ if permitted by the width constraint." This problem appears only when the value is close to zero, otherwise the output is fine: > (format t "~5f" 1.00000001) 1.0 ;; OK I guess those zero digits are not considered trailing because there is no non-zero digit before but I think the specification still requires the fraction to be printed with a single zero digit after the decimal point. Regards, Carlos Ungil

2 1

[armedbear-devel] Using ASDF/BUNDLE for ABCL
by Erik Huelsmann 01 Apr '13

01 Apr '13

Hi, Some time ago Mark Evenson created ASDF-JAR on ABCL. It has some issues packaging ASD files which uses #. syntax to read e.g. version files (version.lisp-sexp) such as bordeaux-threads does. We know ECL started hooking into the ASDF/BUNDLE machinery for ASDF to overcome problems like these. Could you help me/us out and explain how we can plug ABCL into the same machinery? From what I've seen, it's most efficient if the resulting code be committed to ASDF. That's fine by me. At this point, I'd just be happy with an explanation on how to do the hooking up: the new ASDF/BUNDLE functionality doesn't seem to be documented in the manual yet. Thanks for any help you may be able to provide! Bye, Erik.

2 3

[armedbear-devel] How to .... generate abcl-diff9.html?
by Erik Huelsmann 30 Mar '13

30 Mar '13

Hi Anton, The test run has completed. How do I generate a new difference report? Bye, Erik.

2 1

[armedbear-devel] test results for 1.2.0-dev
by Anton Vodonosov 29 Mar '13

29 Mar '13

Hello. Got the test results from Erik's machine few days ago, but only now have time to report them to the mailing list. Comparison of 1.1.1 and 1.2.0-dev on quicklisp 2013-03-12: http://common-lisp.net/project/cl-test-grid/abcl/abcl-diff3.html It doesn't present big difference as I hoped, because closer-mop now compiles on any version of ABCL, including 1.1.1. Maybe runtime behavior will be different, but we have no test suites which highlight this difference. Note some regressions: uiop, metacopy-with-contextl, xcvb-bridge. I haven't analyzed what is the cause. Probably something ASDF-related. To give you sense of ABCL progress, here is the report comparing ABCL 1.1.1 on two quicklisps: 2013-02-17 and 2013-03-12: http://common-lisp.net/project/cl-test-grid/abcl/abcl-diff4.html As you see, much more libraries compile OK in new quicklisp. Note, these two quicklisps were tested on different machines, and the later quicklisp was tested with absence of gcc. This explains failure of cl-gss for example, which can be ignored. Pay attention to some CRASH results in new quicklisp. These crashes reproduce in 1.2.0-dev too and are caused by various errors in ABCL (like index out of bounds, assertion failed). Command line to reproduce it at the cl-test-grid.cloud.efficito.com machine, as user testgrid: rm -r .cache/common-lisp/ java -XX:MaxPermSize=1024m -jar /home/testgrid/lisps/abcl/dist/abcl.jar --noinit --nosystem --batch --eval '(require :abcl-contrib)' --load /home/testgrid/quicklisp/setup.lisp --eval '(ql:quickload :cl-l10n)' > log 2>&1 Finally, here is the load failures report for 1.2.0-dev: http://common-lisp.net/project/cl-test-grid/abcl/abcl-1-2-0-load-failures.h… Recall, that the default sorting in this report tries to present on top the libraries fixing which will give bigger "outcome". More detailed explanation of the report columns is here: https://github.com/cl-test-grid/cl-test-grid/tree/master/reporting#combinin… As you see, there are several directions to dig further, depending on what you are more interested to start with. Let me know what other reports you want to see, or what configurations to test, or how to reproduce certain errors. Best regards, - Anton

3 17

[armedbear-devel] Fwd: cl-l10n: GETENV on ABCL
by Erik Huelsmann 26 Mar '13

26 Mar '13

---------- Forwarded message ---------- From: Attila Lendvai <attila.lendvai(a)gmail.com> Date: Tue, Mar 26, 2013 at 6:28 AM Subject: Re: cl-l10n: GETENV on ABCL To: Erik Huelsmann <ehuels(a)gmail.com> Cc: Armed Bear <armedbear-devel(a)common-lisp.net> hi Erik, > cl-l10n seems to lack a GETENV for ABCL. > Could you use the the function > EXT:GETENV for it? sure, pushed. thanks! -- attila Notice the erosion of your (digital) freedom, and do something about it! PGP: 2FA1 A9DC 9C1E BA25 A59C 963F 5D5F 45C7 DFCD 0A39

1 0

[armedbear-devel] Bordeaux-threads test hangs
by Erik Huelsmann 25 Mar '13

25 Mar '13

>From a mail by Stellian Ionescu: From: Stelian Ionescu <sionescu(a)cddr.org> To: armedbear-devel(a)common-lisp.net Cc: Date: Sat, 23 Mar 2013 01:07:04 +0000 (UTC) Subject: Bordeaux-threads test hangs The B-T test suite hangs on test "condition-variable". If I do a ^C ABCL exits, so I'm not sure how to debug it. CL-USER(1): (lisp-implementation-version) "1.1.1" "OpenJDK_64-Bit_Server_VM-Oracle_Corporation-1.7.0_17-b02" "amd64-Linux-3.7.10-10-default"

4 5

[armedbear-devel] cl-l10n: GETENV on ABCL
by Erik Huelsmann 24 Mar '13

24 Mar '13

Hi Attila, cl-l10n wants to use GETENV. Now that ABCL seems to support closer-mop rather well, we're testing many more libraries to see if they're loading correctly on ABCL. cl-l10n seems to lack a GETENV for ABCL. Could you use the the function EXT:GETENV for it? Example: (ext:getenv "PATH") --> "some path string" Or NIL if no env var by the given name exists. Thanks in advance! Bye, Erik.

1 0

[armedbear-devel] ASDF: Cannot handle the special form EXTENSIONS:TRULY-THE
by Blake McBride 24 Mar '13

24 Mar '13

Greetings, Trying to load a package with ASDF I ran into the following error: ASDF could not load because Cannot (currently) handle the special form EXTENSIONS:TRULY-THE. #<THREAD "interpreter" {4BC78066}>: Debugger invoked on condition of type SIMPLE-ERROR Cannot (currently) handle the special form TRULY-THE Restarts: ... I traced the problem to ASDF and not the package I was attempting to load. Does anyone know anything about this? (I am running the latest SVN head of ABCL) Thanks. Blake McBride

6 14

[armedbear-devel] preparing to test ABCL trunk
by Anton Vodonosov 19 Mar '13

19 Mar '13

Today Erik configured for me a VM on his server, where I can run cl-test-grid tests. We were trying the recent ABCL trunk (1.2.0-dev-svn-14436) on the very very recent quicklisp 2013-03-12, which includes long awaited releases for closer-mop and cffi with ABCL patches. Some notes I collected: 1. New CFFI tries to (require :jss) and fails, because (require :abcl-contrib) hasn't been done. If we do (require :abcl-contrib) then CFFI loads. 2. But when we test actual work, for example by doing (ql:quickload :drakma) (drakma:http-request "https://google.com/") it fails with strange error "UNDEFINED-FUNCTION is called". On SBCL these calls work. 3. (ql:quickload "cl-l10n") fails with ArrayIndexOutOfBounds - may be an ABCL bug. Aside from this, closer-mop seems working (at leas compilation of dependent library "access" doesn't fail anymore). Mark, If you want to quickly reproduce the above problems, you can access the server at cl-test-grid.cloud.efficito.com. Username - testgrid. Erik have added your ssh public key from common-lisp.net to that server. To start ABCL you can use rlwrap java -jar ~/lisps/abcl/dist/abcl.jar (ql:quickload :cl-l10n) => ERROR: java.lang.ArrayIndexOutOfBoundsException: 0 Before starting cl-test-grid tests, I would like to understand, should cl-test-grid always pass --eval "(require :abcl-contrib)" parameter to ABCL when starting it to run a test? Previously cl-test-grid only tested pure ABCL, without contribs. Feedback on this question is very welcome. Best regards, - Anton

3 4

[armedbear-devel] Gray streams aren't streams
by James M. Lawrence 12 Mar '13

12 Mar '13

...they're just grays :) (require :gray-streams) (subtypep 'gray-streams:fundamental-stream 'stream) ;; => NIL, T This doesn't matter for flexi-streams and other libs, but cl-store has a few DECLAREs. I don't know exactly when a type declaration is an assertion in ABCL, but at least it is for a stream with nonzero safety. Best, lmj

3 3

[armedbear-devel] Tests broken?
by Rudolf Schlatte 06 Mar '13

06 Mar '13

Hi, Seems our tests are currently broken - e.g., the (asdf:operate 'asdf:load-op :abcl) form on line 994 of build.xml fails for me. Does this ring a bell for anyone? Rudi

2 2

[armedbear-devel] ASDF 2.32 released
by Faré 06 Mar '13

06 Mar '13

Dear ABCL hackers, ASDF 2.32 was released in time for inclusion in the upcoming CCL 1.9. Once again, we invite all implementation vendors and distributors to upgrade the version of ASDF included in their releases. Yes, I know, that's a lot of releases in a bit more than a month. But it was also a lot of development, and a lot of adjustment to reality after that development was first released. We will keep fixing bugs and improve ASDF based on our growing internal test suite and results from Anton Vodonosov's cl-test-grid. This is still a pre-release for ASDF3. Here are the changes, since previous release 2.31, and since previous public announcement for 2.30. >From 2.31 to 2.32: * deferred-warning checks are now disabled by default, to enhance backward compatibility with ASDF 2.26 and earlier. In the future, we will enable them by default, but not until we implement a smoother transition plan. Also, CCL-specific fixes to deferred-warning support. * UIOP is the new official name for ASDF-DRIVER. "Utilities for Implementation- and OS- Portability". Old names remain as package and system nicknames: ASDF/DRIVER ASDF-DRIVER ASDF-UTILS * require-system so systems may depend on implementation-provided modules. * auto-upgrade attempt in operate *before* the implicit find-system. * class specification for components can now be a string to be read as a symbol. * feature conditional dependencies are now debugged and tested: :depends-on ("some-system" (:feature :foo "other-system)) we only recommend them for dependencies between systems; within systems, we recommend you use feature-conditional components with :if-feature :foo and we only provide limited support for the deprecated legacy way of using feature-conditionals with a module having :if-component-dep-fails :ignore while its components specify things like: :in-order-to ((compile-op (feature :foo))) * read-from-file for :version specification is made more useful by using the ASDF-USER package rather than CL (into which interning is forbidden) to read the files. Changes from 2.30 to 2.31: * *default-encoding* is now UTF-8. As tested with cl-test-grid, This is a boon for most programs, that will compile in a more predictable way in a wider range of settings. A handful of unmaintained outliers still need to be fixed. * Downgrade is now explicitly avoided. ASDF will issue a warning if your system is misconfigured in a way that specifies downgrade, but will then ignore the specified ASDF downgrade. * version specifications, when invalid, will lead only to a warning for now; a future ASDF3 may restore the behavior of ASDF 2.27, that raises an errors when there is a bad :version specification, but for now, backward compatibility prevails. * ECL support received several bug fixes. * precompiled-system support was notably fixed, enabling single-fasl deployment of SBCL contribs. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org The rule is, jam to-morrow and jam yesterday, but never jam today. — Lewis Carroll

2 1

[armedbear-devel] [Extended Deadline] European Lisp Symposium 2013 - Madrid - June 1-4
by Didier Verna 05 Mar '13

05 Mar '13

;; ______ _ _____ _ __ ____ ;; | ____| | | / ____| ( ) /_ | |___ \ ;; | |__ | | | (___ |/ | | __) | ;; | __| | | \___ \ | | |__ < ;; | |____ | |____ ____) | | | ___) | ;; |______| |______| |_____/ |_| |____/ ;; ;; European Lisp Symposium 2013 - ELS'13 ;; Madrid, Spain ;; ;; June 1-4, 2013 ;; ;; http://els2013.european-lisp-symposium.org/ ** DEADLINE EXTENSION: March 17th ** The purpose of the European Lisp Symposium is to provide a forum for the discussion and dissemination of all aspects of design, implementation and application of any of the Lisp and Lisp-inspired dialects, including Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure, ACL2, ECMAScript, Racket, SKILL, Hop and so on. We encourage everyone interested in Lisp to participate. The main theme of the 2013 European Lisp Symposium is on the use of these languages with respect to the current grand challenges: big tables, open data, semantic web, network programming, discovery, robustness, runtime failures, etc. The European Lisp Symposium 2013 solicits the submission of papers with these specific themes in mind, alongside the more traditional tracks which have appeared in the past editions. We invite submissions in the following forms: Papers: Technical papers of up to 15 pages that describe original results or explain known ideas in new and elegant ways. Demonstrations: Abstracts of up to 4 pages for demonstrations of tools, libraries, and applications. Tutorials: Abstracts of up to 4 pages for in-depth presentations about topics of special interest for at least 90 minutes and up to 180 minutes. Lightning talks: Abstracts of up to one page for talks to last for no more than 5 minutes. 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. Invited speakers: Florian Loitsch, Google: Dart, why you should care. Gérard Assayag, Ircam: Lisp and Music Research. Important dates: March, 17th 2013: submission deadline ** EXTENDED ** April, 5th 2013: acceptance results June, 1-4 2013: symposium Program Commitee: Pascal Costanza, Intel, Belgium Ludovic Courtes, INRIA, France Theo D'Hondt, Vrije Universiteit Brussel, Belgium Florian Loitsch, Google, Denmark Christian Queinnec, UPMC, France Kurt Noermark, Aalborg University, Denmark Olin Shivers, Northeastern University, USA Manuel Serrano, INRIA, France Didier Verna, EPITA, France Chair: Juan Jose Garcia-Ripoll, local organizer Christian Queinnec, PC co-chair Manuel Serrano, PC co-chair -- Resistance is futile. You will be jazzimilated. Scientific site: http://www.lrde.epita.fr/~didier Music (Jazz) site: http://www.didierverna.com

1 0

[armedbear-devel] Fwd: variable-information?
by Erik Huelsmann 03 Mar '13

03 Mar '13

---------- Forwarded message ---------- From: James M. Lawrence <llmjjmll(a)gmail.com> Date: Sat, Mar 2, 2013 at 5:21 PM Subject: Re: [armedbear-devel] variable-information? To: Erik Huelsmann <ehuels(a)gmail.com> On Sat, Mar 2, 2013 at 10:38 AM, Erik Huelsmann <ehuels(a)gmail.com> wrote: > Hi James, > > Are you in a macro expansion environment? If that's the case, then we could > quite easily make that available, I'm sure. > > Could you provide a bit more detail on what your usecase is? (I'm not > familiar with cltl2, I'm affraid) Hi, Yes by environment I mean the &environment parameter to defmacro. The distributed version of lparallel uses variable-information to create closures which are executed on remote machines. Since at least four implementations offer variable-information (SBCL, CCL, LispWorks, Allegro), this technique amounts to a somewhat portable way to serialize closures. [Did you mean to respond to the list?] Regards, lmj

1 0

[armedbear-devel] variable-information?
by James M. Lawrence 02 Mar '13

02 Mar '13

Is there something akin to variable-information in CLTL2? For a given environment I would like to know if a symbol is a lexical variable or a symbol macrolet.

2 1

[armedbear-devel] Package-local nicknames landed
by Rudolf Schlatte 01 Mar '13

01 Mar '13

Hi, I just committed support for package-local nicknames in abcl. This follows the lead of sbcl and lets you introduce short, meaningful nicknames ("XML" for "COM.WHATEVER.FOO.XML-PARSER") in your own packages without fear of package (nick)name collisions. Here's the example from Nikodemus' documentation: (defpackage :bar (:intern "X")) (defpackage :foo (:intern "X")) (defpackage :quux (:use :cl) (:local-nicknames (:bar :foo) (:foo :bar))) (find-symbol "X" :foo) ; => FOO::X (find-symbol "X" :bar) ; => BAR::X (let ((*package* (find-package :quux))) (find-symbol "X" :foo)) ; => BAR::X (let ((*package* (find-package :quux))) (find-symbol "X" :bar)) ; => FOO::X This puts :package-local-nicknames on *features*; I had to increase the fasl version since %defpackage got a new parameter. Cheers, Rudi

2 1