armedbear-devel December 2015

armedbear-devel@common-lisp.net

7 participants
5 discussions

Loops and interruptibility
by Scott L. Burson 30 Dec '15

30 Dec '15

Hi all, The other day I had an inadvertent infinite loop in my code, running in ABCL, and found I was unable to interrupt it with double C-c in SLIME. In fact, even when I killed the process, restarted it, and started the code with the infinite loop in a new thread, I couldn't kill the thread! Is this a known problem, or is something wrong with my setup? -- Scott

2 1

Problems with static methods (and interface implementation?), java.lang.NoClassDefFoundError.
by fsmunoz＠gmail.com 28 Dec '15

28 Dec '15

Hello, I have been struggling with this for some hours now and would welcome some pointers. I'm writing a small how-to on how to deploy Common Lisp web applications (i.e. "something that replies to an HTTP request") in IBM's Bluemix using ABCL. That part is taken care of and I have it up and running (more on that in a separate post). I was going for a more advanced version and I am having a problem with interface implementation. To showcase java interop I am not using CL web frameworks, but decided to give Spark a try (http://sparkjava.com/documentation.html) just to get a minimal example up and running (I already have Jetty working and serving up an "(Hello World)" page): #+BEGIN_SRC java import static spark.Spark.*; public class HelloWorld { public static void main(String[] args) { get("/hello", (req, res) -> "Hello World"); } } #+END_SRC I'm going to start with the Clojure example since that one I got working; the API reference (http://spark.screenisland.com/spark/Spark.html) helped me and this works #+BEGIN_SRC clojure => (Spark/get "/hello" (reify spark.Route (handle [this req res] ("Hello World")))) [Thread-34] INFO spark.webserver.JettySparkServer - == Spark has ignited ... [Thread-34] INFO spark.webserver.JettySparkServer - >> Listening on 0.0.0.0:4567 nil[Thread-34] INFO org.eclipse.jetty.server.Server - jetty-9.3.2.v20150730 #+END_SRC I have learned (thanks to bpalmer in #emacs, cheers!) that the Single Abstract Method can be constructed using Java 8 lambda expressions, which is why I couldn't find a reference to the "handle" method, which I got from the API. Now, back to ABCL; I'm unable to reproduce the above and I'm unsure if it is because I'm not getting something right (likely) or because some of the plumbing in ABCL isn't quite there yet. I tried this using jss::jinterface-implementation (which I had used previously with my MQTT code and worked perfectly): #+BEGIN_SRC lisp (#"get" 'spark.Spark "/hello" (jss::jinterface-implementation "spark.Route" "handle" (lambda (request response) ("Hello World")))) #+END_SRC The (jinterface-implementation ...) returns #<com.sun.proxy.$Proxy5 com.sun.proxy.$Proxy5@4f0bbf2a {41CC48BB}>, but the (#"get"...) fails: Java exception 'java.lang.NoClassDefFoundError: Could not initialize class spark.Spark$SingletonHolder'. I have also tried with jmake-proxy to see if there was something different going on. #+BEGIN_SRC lisp (java::jstatic "get" "spark.Spark" "/hello" (java::jmake-proxy "spark.Route" #'(lambda (lisp-this method request response) ("Hello World")))) #+END_SRC The result is the same, both in what jmake-proxy returns and the final error. Note that I have added the jar to the classpath, otherwise I would get "ClassNotFound". Even more simply this also doesn't work: #+BEGIN_SRC clojure => (Spark/stop) [nREPL-worker-11] INFO spark.webserver.JettySparkServer - >>> Spark shutting down ... #+END_SRC ... (#"stop" 'spark.Spark) returns the same "NoClassDefFoundError", which makes me thing the issue is not with the jproxy bit but something more fundamental... With this in mind: 1) Is there anything obviously wrong about the way I'm going about it - not limited to implementation errors on my part but including trying to use parts of ABCL's Java interop which aren't done? 2) The java::jmake-proxy call... I wasn't able to find a single example of it used (the only code I find when searching is the implementation itself) so I'm not sure I'm understanding the documentation correctly: are the arguments I'm using above correct? I'm using the method that uses a function and if I understood it correctly the first argument is "lisp-this" (which defaults to nil), the second the method name (which would be "handle" in this example, and the rest are the method arguments (request and response here). I am of course available for any further clarification, and if this is something that isn't obvious I can upload a minimal example using quickproject and quicklisp. Best regards, -- Frederico Muñoz fsmunoz(a)gmail.com

1 0

destructuring-bind not signaling error with &rest
by 2l8qyo+d734u52o8x7j0＠guerrillamail.com 22 Dec '15

22 Dec '15

(destructuring-bind (a b &rest c) '(1) b) => nil with no error. sbcl, clisp, and ecl signal an error. http://clhs.lisp.se/Body/m_destru.htm seems to suggest it should be an error. version is abcl 1.3.3 on jdk 1.8.0_66 ---- Sent using GuerrillaMail.com Block or report abuse: https://www.guerrillamail.com/abuse/?a=QFN5AAkCRrUHxQqx5nsTUhfIQMef3JpczrdS…

1 0

ASDF configuration for "JAR-only" system
by John Pallister 16 Dec '15

16 Dec '15

Hello list, I'm trying to configure ASDF to load my application while running within the Google App Engine development server (Jetty 6.1). My Ant build script uses ASDF-JAR:PACKAGE to produce a single JAR file containing my application and all dependencies, and copies this to the war/WEB-INF/lib/ directory so that it's in the classpath. At runtime (in a separate bootstrap.lisp file), following the example of ASDF-JAR:ADD-TO-ASDF[1], I search the application JAR file (obtained by grovelling JAVA:DUMP-CLASSPATH) for the .ASD files and push them all onto ASDF:*CENTRAL-REGISTRY*. So far so good. (Having read the ASDF manual I now know I should either build a .cl-source-registry.cache file into the JAR or compute an ASDF source registry configuration and include that.) When ASDF starts up it tries to read various configuration files from the filesystem, for both the source registry and for its output translations. This isn't allowed by App Engine. On #lisp, Attila Lendvai suggested that giving ASDF a source registry configuration of '(:SOURCE-REGISTRY :IGNORE-INHERITED-CONFIGURATION) should suppress this behaviour, and it does seem to work. Now I'm struggling to get the output translations to work. Based on ADD-TO-ASDF again I'm using an output translations configuration of: `(:output-translations (,(merge-pathnames "/**/*.*" *application-jar-path*)) ; => #P"/**/*.*" :ignore-inherited-configuration :disable-cache) My *APPLICATION-JAR-PATH* is #P"jar:file:/Volumes/SoftRAID/Users/john/src/synchromesh/forumfeedme/war/WEB-INF/lib/forumfeedme-lisp-0.1.0.jar!/", i.e. a pathname with the JAR path as the PATHNAME-DEVICE. With this I get the error "access denied ("java.io.FilePermission" "/___jar___file___root___" "read")". This matches the default translations seen in asdf.lisp:WRAPPING-OUTPUT-TRANSLATIONS: (defun wrapping-output-translations () `(:output-translations ;; Some implementations have precompiled ASDF systems, ;; so we must disable translations for implementation paths. #+(or #|clozure|# ecl mkcl sbcl) ,@(let ((h (resolve-symlinks* (lisp-implementation-directory)))) (when h `(((,h ,*wild-path*) ())))) #+mkcl (,(translate-logical-pathname "CONTRIB:") ()) ;; All-import, here is where we want user stuff to be: :inherit-configuration ;; These are for convenience, and can be overridden by the user: #+abcl (#p"/___jar___file___root___/**/*.*" (:user-cache #p"**/*.*")) #+abcl (#p"jar:file:/**/*.jar!/**/*.*" (:function translate-jar-pathname)) ;; We enable the user cache by default, and here is the place we do: :enable-user-cache)) Although I don't understand exactly how the "JAR file as device" (JFAD) translations are supposed to work, one thing that struck me as odd while investigating things was this: CL-USER> (make-pathname :device (list #P"/foo.jar")) #P"jar:file:/foo.jar!/" CL-USER> (merge-pathnames "**/*.*" *) #P"jar:file:/foo.jar!/**/*.*" CL-USER> (merge-pathnames "/**/*.*" **) #P"/**/*.*" CL-USER> (pathname-directory **) (:RELATIVE :WILD-INFERIORS) CL-USER> (pathname-directory **) (:ABSOLUTE :WILD-INFERIORS) That is, merging a relative path with the (absolute) JFAD path retained the default JAR file "device" (and remains a relative path, which ASDF won't accept), but merging an absolute path reset the device component. I've read through the documentation for MERGE-PATHNAMES in the HyperSpec[2] and AFAICT the device component should be copied across. I'm reasonably confident that if it were, things would work better. But I could be (doubly) wrong. I am trying to figure this out for myself, but I'm stuck for now, so I'm hoping someone (i.e. Mark) can, on reading this, offer some guidance as to where I should go from here. I haven't (yet) tried posting to the ASDF mailing list as this seems like a fairly ABCL-specific issue. I guess the fallback is to unpack the application JAR and just load the FASLs directly, but (based again on ADD-TO-ASDF) I'm pretty sure that this should work, and it does seem to be the Right Thing. Any or all comments and/or advice appreciated, Cheers, John :^P [1] http://abcl.org/trac/browser/trunk/abcl/contrib/asdf-jar/asdf-jar.lisp [2] http://www.lispworks.com/documentation/HyperSpec/Body/f_merge_.htm#merge-pa… -- John Pallister john(a)johnp.net john(a)synchromesh.com

2 3

Package-local nicknames
by Alessio Stalla 09 Dec '15

09 Dec '15

Hello list, long time no see :) I'm once again experimenting on ABCL with a sort of a pet peeve of mine: hierarchical symbols (aka symbols as packages aka symbol/package conflation). If I get good results I'll submit an article to the next ELS. Btw, is anyone going? I've seen that, since the time when I was actively contributing to it, ABCL has gained package-local nicknames (or, they were already there and I never noticed or I forgot about them). Since my experiment is, I suppose, a superset of what said nicknames have to offer, I'm curious: is anybody using them? How? Are they a novel idea of ABCL's, or were they inspired by other implementations? Do they implement some specification (e.g., a CDR)? Thanks for any input! Cheers Alessio

5 7

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-devel December 2015