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

[armedbear-devel] Desperate for a chance to hack with ABCL all day
by ubikation _ 08 Apr '15

08 Apr '15

Greetings! As you may know from my ramblings I'm new to Common Lisp and ABCL in particular. I'm not an experienced coder but I'm really enjoying the time I'm spending becoming more familiar with ABCL/Slime/Emacs. Would anybody be interested in me working for them for a low ($15) hourly contract? I really am desperate for work and and a chance to prove myself. Thank you very much for your time and consideration. I am happy to give more personal information for anybody who is interested.

1 0

[armedbear-devel] Hadoop Anyone?
by Steven Núñez 08 Apr '15

08 Apr '15

Greetings All, I’ve got another ‘big data’ project on the go, and rather than program in Java, I thought I’d give LISP a go. There are ways to program Hadoop with Clojure<http://alexott.net/en/clojure/ClojureHadoop.html>, but I’d rather not learn a non-standard lisp if I can avoid it. Has anyone got ABCL working as a Hadoop map/reduce program? I’d prefer native, but streaming will do if need be. Regards, - SteveN

1 0

[armedbear-devel] ensure-parsed-mvn not yet exported in abcl-asdf.lisp
by Cyrus Harmon 08 Apr '15

08 Apr '15

The recent addition of the asdf:ensure-parsed-mvn call in the RESOLVE defmethod form has the problem that the ensure-parsed-mvn symbol isn’t exported at the time the defmethod is compiled. Assuming that the intended behavior of export is not to change things at compile time, we need to wrap the export call in an appropriate eval-when form. The following seems to fix things for me: diff --git i/contrib/abcl-asdf/abcl-asdf.lisp w/contrib/abcl-asdf/abcl-asdf.lisp index 401487b..b96457e 100644 --- i/contrib/abcl-asdf/abcl-asdf.lisp +++ w/contrib/abcl-asdf/abcl-asdf.lisp @@ -85,8 +85,9 @@ (defun ensure-parsed-mvn (component) (setf path (format nil "~A/~A/~A" group-id artifact-id version)))) component)) -(export `(mvn iri ensure-parsed-mvn group-id artifact-id version) - 'asdf) +(eval-when (:compile-toplevel :load-toplevel :execute) + (export `(mvn iri ensure-parsed-mvn group-id artifact-id version) + 'asdf)) (defmethod source-file-type ((component iri) (system system)) nil)

2 2

[armedbear-devel] abcl 1.2.1 ignores :resolve-symlinks parameter of directory
by Gabor Balazs 08 Apr '15

08 Apr '15

hY, Armed Bear Common Lisp 1.2.1 Java 1.6.0_27 Sun Microsystems Inc. OpenJDK 64-Bit Server VM ls -l -rw-r--r-- 1 user group 0 Dec 15 11:00 file lrwxrwxrwx 1 user group 4 Dec 15 11:00 link -> file CL-USER(3): (directory "./*" :resolve-symlinks nil) (#P"/home/user/test/file" #P"/home/user/test/file") The result should be (#P"/home/user/test/file" #P"/home/user/test/link"). Or do I miss something? Thanks, `bg`

1 0

[armedbear-devel] Link from Twitter
by Mark Evenson 08 Apr '15

08 Apr '15

www.oracle.com/technetwork/java/javase/7u25-relnotes-1955741.html Download the official Twitter app here Sent from my iPad

1 0

[armedbear-devel] bogus (t ...) function call
by Cyrus Harmon 08 Apr '15

08 Apr '15

I finally realized where the warning about calling the undefined function T was coming from: diff --git a/contrib/abcl-asdf/abcl-asdf.lisp b/contrib/abcl-asdf/abcl-asdf.lisp index b96457e..2ded8b5 100644 --- a/contrib/abcl-asdf/abcl-asdf.lisp +++ b/contrib/abcl-asdf/abcl-asdf.lisp @@ -130,8 +130,7 @@ (defmethod resolve ((mvn-component asdf::mvn)) (resolve-dependencies group-id artifact-id version) (if alternate-uri (values (namestring alternate-uri) alternate-uri) - (t - (error "Failed to resolve MVN component name ~A." name)))))) + (error "Failed to resolve MVN component name ~A." name))))) (defmethod resolve ((uri pathname)) (warn "Unimplemented.")) Looks like this was copy/pasted from a cond form elsewhere. Cyrus

1 1

[armedbear-devel] Re: cl-test-grid: Testing ABCL-1.2.0-RC
by Mark Evenson 08 Apr '15

08 Apr '15

Agreed: fixing STD-FIND-METHOD-COMBINATION seems to be necessary. @anton: thanks for the tests @rudi: dunno if this is you, but could you take a look to see if this is easy? If you fix on trunk, I will take care of the release. At this point, I would release abcl-1.2.1 and announce, as abcl-1.2.0 has already been "softly launched" without announcement. -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad idea? A: Top-posting. Q: What is the most annoying thing in email? On Jun 9, 2013, at 1:15, Anton Vodonosov <avodonosov(a)yandex.ru> wrote: > 08.06.2013, 02:35, "Anton Vodonosov" <avodonosov(a)yandex.ru>: >> 08.06.2013, 02:13, "Erik Huelsmann" <ehuels(a)gmail.com>: >> >>> Hi Anton, >>> Could you test ABCL-1.2.0-RC with the latest Quicklisp snapshot and publish reports? I'd love to see how we're doing in the CL ecosystem before we release! >>> >>> Thanks! >>> >>> Bye, >>> >>> Erik. >> >> Hello, Erik. >> >> Just today I started the tests, on the 1.2.0 source tarball from abcl.org and on the current svn head. >> They are running on your VM. The results will be a day or two later. >> >> Best regards, >> - Anton > > Hello again. > > The results for ABCL 1.2.0 RC (the soruce tarball form abcl.org) are ready. > Comparision with ABCL 1.1.1: > http://common-lisp.net/project/cl-test-grid/abcl/abcl-diff10.html > > As you see there are some regressions - results that were green and have become red. > Most of the seem to be caused by the same error: Wrong number of arguments for #<STD-FIND-METHOD-COMBINATION {17D2F0E}>. > > Best regards, > - Anton

5 7

[armedbear-devel] Fix MAKE-FUNCTION-POINTER for abcl-1.2.1 with jna-4.0.0.
by Mark Evenson 08 Apr '15

08 Apr '15

A [fix for CFFI with function pointers when using jna-4.0.0][1] and [the corresponding naked diff][2]. Can’t quite seem to figure out how to make a “pull request” out of this. *sigh* [1]: https://github.com/easye/cffi/commit/0f63798ab20e274d3062964a3286e34855747d… [2]: http://slack.net/~evenson/abcl/cffi/abcl-cffi-encoding-20131124a.diff -- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."

1 0

[armedbear-devel] FIND-SYSTEM-JAR ignores versioned jars
by Olof-Joachim Frahm 08 Apr '15

08 Apr '15

Hi, I've noticed (while building with Maven), that the versioned system and contrib jars aren't found properly because of how the loader constructs the pathnames. Attached are three patches to clean up abcl-contrib.lisp a bit and then fix this by accepting every matching pathname directly. This still doesn't check for the correct version string, but maybe that's not a problem. Best regards, Olof

2 3

[armedbear-devel] COMPILE-FILE fails with stack overflow when INLINE meets recursion
by Xiaofeng Yang 08 Apr '15

08 Apr '15

Hi, all. It seems that cl-prime-maker compiles failed with ABCL because of the following bug. This bug can also be found in ABCL 1.1.1 (I don't know whether this bug can be found in 1.1.0 or earlier), not only 1.2.x and 1.3.x. $ cat bug-for-abcl.lisp (in-package :cl-user) (declaim (inline foo)) (defun foo () (foo)) (defun bar () (foo)) $ ~/abcl/abcl Armed Bear Common Lisp 1.3.0 Java 1.8.0 Oracle Corporation Java HotSpot(TM) 64-Bit Server VM Low-level initialization completed in 0.364 seconds. Startup completed in 1.739 seconds. Type ":help" for a list of available commands. CL-USER(1): (compile-file "bug-for-abcl.lisp") ; Compiling /tmp/bug-for-abcl.lisp ... ; (IN-PACKAGE :CL-USER) ; (DECLAIM (INLINE FOO)) ; (DEFUN FOO ...) ; (DEFUN BAR ...) #<THREAD "interpreter" {776DDE2A}>: Debugger invoked on condition of type STORAGE-CONDITION Stack overflow. Restarts: 0: TOP-LEVEL Return to top level. [1] CL-USER(2): After the stack overflow, if I returned to the top level, remove the line "(declaim (inline foo))" and COMPILE-FILE again, it also failed. Unless I restart ABCL and perform COMPILE-FILE with the file without the line "(declaim (inline foo))", it can be compiled now. Best regards, Xiaofeng Yang

2 1