armedbear-devel March 2013

armedbear-devel@common-lisp.net

11 participants
17 discussions

[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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-devel March 2013