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

[armedbear-devel] [CfP] International Lisp Conference, Aug. 14-17 2014, Montréal, Canada
by Didier Verna 08 Apr '15

08 Apr '15

ILC 2014 - International Lisp Conference "Lisp on the Move" August 14-17 2014, Université de Montréal, Montréal, Canada Sponsored by the Association of Lisp Users http://www.international-lisp-conference.org Scope: Lisp is one of the greatest ideas from computer science and a major influence for almost all programming languages and for all sufficiently complex software applications. The International Lisp Conference is a forum for the discussion of Lisp and, in particular, the design, implementation and application of any of the Lisp dialects. We encourage everyone interested in Lisp to participate. We invite high quality submissions in all areas involving Lisp dialects and any other languages in the Lisp family, including, but not limited to, ACL2, AutoLisp, Clojure, Common Lisp, ECMAScript, Dylan, Emacs Lisp, ISLISP, Racket, Scheme, SKILL, HOP etc. This year's focus will be directed towards integrated solutions, including mobile computing. We especially invite submissions in the following areas: * Pervasive computing * Interoperability * Portability * Implementation challenges/tradeoffs for embedded/mobile platforms * Language support for mobile toolkits and frameworks * Language support for distribution * Language support for reliability, availability, and serviceability * Mobile IDEs * Mobile applications Contributions are also welcome in other areas, including but not limited to: * Language design and implementation * Language integration, inter-operation and deployment * Applications (especially commercial) * Reflection, meta-object protocols, meta-programming * Domain-specific languages * Programming paradigms and environments * Efficient parallel and concurrent computation * Language support for managing both manual and automatic GC * Theorem proving * Scientific computing * Data mining * Semantic web Technical Programme: Original submissions in all areas related to the conference themes are invited for the following categories: Papers: Technical papers of up to 10 pages that describe original results. Demonstrations: Abstracts of up to 2 pages for demonstrations of tools, libraries and applications. Workshops: Abstracts of up to 2 pages for groups of people who intend to work on a focused topic for half a day. Tutorials: Abstracts of up to 2 pages for in-depth presentations about topics of special interest for 1 to 2 hours. Panel discussions: Abstracts of up to 2 pages for discussions about current themes. Panel discussion proposals must mention panel member who are willing to partake in a discussion. The conference will also provide slots for lightning talks, to be registered on-site every day. For inquiries about any other kind of participation (commercial exhibits, advertising, prizes, book signing etc.), please see the contacts below. Important Dates: - May 18, 2014: Submission deadline - June 09, 2014: Notification of acceptance - June 29, 2014: Final Papers due - August 14, 2014: Conference 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. Submissions should be uploaded to Easy Chair, at the following address: https://www.easychair.org/conferences/?conf=ilc14 Organizing Committee: General Chair: Marc Feeley (Université de Montréal, Montréal, Canada) Programme Chair: Didier Verna (EPITA Research lab, Paris, France) Local chair: Marc Feeley (Université de Montréal, Montréal, Canada) Programme Committee: to be announced Contacts: * General Questions: ilc14-organizing-committee at alu.org * Programme Committee: ilc14 at easychair.org For more information, see http://www.international-lisp-conference.org -- Resistance is futile. You will be jazzimilated. Lisp, Jazz, Aïkido: http://www.didierverna.info

1 0

[armedbear-devel] EXT:URL-PATHNAME vs http: as a logical pathname
by Karsten Poeck 08 Apr '15

08 Apr '15

Hello all, I am trying to compile cl-http on abcl. Mostly got it loading, but have some problems with abcls url-pathnames. Example: CL-USER> (lisp-implementation-version) "1.2.1" "Java_HotSpot(TM)_64-Bit_Server_VM-Apple_Inc.-1.6.0_51-b11-456-11M4508" "x86_64-Mac_OS_X-10.8.4" CL-USER> (lisp-implementation-type) "Armed Bear Common Lisp" CL-USER> (setf (logical-pathname-translations "http") '( ("port;**;*.*" "/Users/karstenpoeck/Documents/workspace/trunk/contrib/kpoeck/port-templa te/**/*.*") ("**;*.*" "/Users/karstenpoeck/Documents/workspace/trunk/**/*.*") ) ) ((#P"HTTP:PORT;**;*.*" #P"/Users/karstenpoeck/Documents/workspace/trunk/contrib/kpoeck/port-temp late/**/*.*") (#P"HTTP:**;*.*" #P"/Users/karstenpoeck/Documents/workspace/trunk/**/*.*")) ;;;; the problem is here CL-USER> (translate-logical-pathname "http:declaration.lisp") #P"http:" If I do the same with httpx: instead of http:, the code loads fine. The reason is probably the following. CL-USER> (type-of (pathname "http:declaration.lisp")) URL-PATHNAME Later starting up cl-hhtp i get: http:www;foo.html has a null authority. http:www;foo.html has a null authority. http:proxy-cache; has a null authority. http:pw;random-seed.lisp has a null authority. java.lang.NullPointerException at sun.net.www.ParseUtil.toURI(ParseUtil.java:261) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnectio n.java:905) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.jav a:836) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnect ion.java:1172) at java.net.URL.openStream(URL.java:1010) at org.armedbear.lisp.Pathname.getInputStream(Pathname.java:2369) .... I completely understand that it is desirable to have (load "http://beta.quicklisp.org/quicklisp.lisp") working, but can't you check for "http://" or "https://" before converting a pathname to an url-pathname? Karsten

2 2

[armedbear-devel] Unsubscribe
by Wayne Rogers 08 Apr '15

08 Apr '15

2 1

[armedbear-devel] Status of 1.2.0
by Erik Huelsmann 08 Apr '15

08 Apr '15

Hi Mark, all, My own testing didn't reveal any notable problems, nor did the ANSI test suite. There are a few regressions in cl-test-grid which indicate our changes to symbol interning. My proposal is to go forward with the 1.2 release and release a bugfix as soon as we identify and fix the problem which the cl-colors tests indicate. What's your position? -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

2 12

[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