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

[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] patch for automagical JAR loading
by Milos Negovanovic 30 Jan '13

30 Jan '13

Hi all, patch is attached. With it this kind of .asd spec works out of the box and resolves all JARs and puts them in classpath: (require :asdf) (require :abcl-contrib) (require :abcl-asdf) (require :jss) (asdf:defsystem #:test-asdf :serial t :description "" :author "" :license "Specify license here" :components ((:module jetty :serial t :components ((:mvn "org.eclipse.jetty/jetty-server/8.1.8.v20121106") (:mvn "org.freemarker/freemarker/2.3.19"))) (:module source :pathname "" :serial t :components ((:file "package") (:file "example")) :depends-on (:jetty)))) The bug is someplace in abcl-asdf:resolve ... didnt figure out where, i just used abcl-asdf:resolve-dependencies ... not sure why you want resolving code in 2 places anyway :). Regards -- Milos Negovanovic milos.negovanovic(a)gmail.com

1 0

[armedbear-devel] patch for runtime-class.lisp
by Milos Negovanovic 29 Jan '13

29 Jan '13

Hi all, As mentioned on #abcl on freenode, I needed the following patch to make my simple jetty example work. Patch is attached. Example for which I needed this is at: http://paste.lisp.org/display/134966 Regards -- Milos Negovanovic milos.negovanovic(a)gmail.com

2 1

[armedbear-devel] ASDF support for deferred warnings in ABCL?
by Faré 27 Jan '13

27 Jan '13

Dear ABCL developers, I've been adding support for ASDF to save deferred warnings (typically, forward function references) in a file, so that if you do an incremental compilation, warnings from previously compiled files are still correctly handled at the end of the virtual with-compilation-unit. I've added support for SBCL and CCL myself, which was made much easier by being able to read the source code to their compilers, but I don't feel like groveling through four more free sofware compilers. Would you be interested in implementing the same feature for ABCL, or at least in guiding me on how to do so? The code is mainly in asdf/lisp-build.lisp functions reify-deferred-warnings unreify-deferred-warnings reset-deferred-warnings. http://common-lisp.net/gitweb?p=projects/asdf/asdf.git Best regards, —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org I don't know if might makes right, but lack of might sure makes lack of right.

2 1

[armedbear-devel] abcl-1.1.0 vs. abcl-1.1.0.2 known differences
by Mark Evenson 26 Jan '13

26 Jan '13

To address a question that came up on #abcl: what is the difference between the abcl-1.1.0 and abcl-1.1.0.2 releases? The short answer is that there should be no difference. The release of abcl-1.1.0 (and accompanying signatures) were updated "in-place" within twenty-four hours of their release. As stated in the abcl-1.1.0.2 release announcement, the only known initial difference between the 1.1.0 and 1.1.0.2 releases of ABCL was that somehow the ABCL-CONTRIB ASDF definition in 1.1.0 was syntactically invalid as it included an extra comma (",") character preventing it from loading. After this was discovered, the abcl-1.1.0 release was rebuilt and "updated" in place on common-lisp.net. Because googlecode requires that published URIs point idempotently to their resources over time (probably to make universal distribution easier) a release designated abcl-1.1.0.2 release was made to googlecode.com If there are any observed differences between the two releases, I would appreciate knowing more details accompanied by information on how the distribution was obtained. -- "A screaming comes across the sky. It has happened before, but there is nothing to compare it to now."

1 0

[armedbear-devel] Upgrade issues
by Faré 24 Jan '13

24 Jan '13

ABCL is one of the three implementations, together with CLISP and CMUCL, where I ultimately punted on ASDF hot-upgrade, by just trying to rename away the ASDF package if it's too old. I don't know if you're interested in making the kind of package surgery I was indulging in work, but it involves rehoming symbols from ASDF to subpackages such as ASDF/COMPONENT, including for class slot names. Anyway, please test the latest ASDF with ABCL, I think it's ripe for release, but I'd like your feedback considering the massive amount of hacking that happened. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org If the human mind were simple enough to understand, we'd be too simple to understand it. — Pat Bahn

4 7

[armedbear-devel] Android support?
by Andrew Pennebaker 22 Jan '13

22 Jan '13

What's the state of Android support for ABCL? Can we have some demo apps and tutorials? It would be awesome to write mobile apps in Lisp! -- Cheers, Andrew Pennebaker www.yellosoft.us

1 0

Re: [armedbear-devel] [asdf-devel] CMUCL fails tests (Was Re: Just pulled an update and now CCL fails the tests)
by Faré 20 Jan '13

20 Jan '13

> I guess its yet another issue with merging with *d-p-d* which defaults > to #p"" (current directory) on cmucl. > > Ray > Yup. Fixed. Which reminds me I have no implementation of getcwd for ABCL or GCL; I don't know what type it returns on Corman. ABCL hackers: is there such a thing as getcwd in ABCL, and if so how do I get to it? —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org A pretty face is not a passport; it's a visa and it runs out fast.

2 1

[armedbear-devel] Pre ASDF-2.27 failing to compile on ABCL
by Mark Evenson 15 Jan '13

15 Jan '13

On 1/11/13 5:53 PM, Faré wrote: > Dear Lisp hackers, > > I've completed yet another major pass of refactoring of ASDF. […] Coolness! Keep it coming! Failing to compiled the concatenated fasl from ASDF master tip (local : UNDEFINED-FUNCTION: ;COMMON-LISP:CELL-ERROR-NAME triggers autoloading of org.armedbear.lisp.cell_error_name ... ; Autoloaded org.armedbear.lisp.cell_error_name (0.0050 seconds) The function ASDF/PACKAGE::WHEN-FISHY is undefined. Have I missed some packaging in the implemenation (abcl-1.2.0-dev)? ABCL trunk currently has some problems with autoloading (some) COMMON-LISP functions via SETF expanders, which I am in the process of fixing. ; SLIME 2012-11-23 CL-USER> (lisp-implementation-version) "1.2.0-dev" "Java_HotSpot(TM)_64-Bit_Server_VM-Sun_Microsystems_Inc.-1.6.0_37-b06" "amd64-SunOS-5.11" Thanks, Mark <evenson(a)panix.com>

1 0

[armedbear-devel] function (setf documentation) has disappeared
by Eric Marsden 06 Jan '13

06 Jan '13

Hi, It seems that the DEFSETF for DOCUMENTATION has disappeared recently. -- Eric Marsden

2 3