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
In cooperation with: ACM SIGPLAN
http://www.international-lisp-conference.org
Latest News:
* The submission deadline has been extended to May 25. You have one more
week to write a paper!
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. The
conference proceedings will be published in the ACM Digital Library.
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 25, 2014: Submission deadline *** EXTENDED ***
- 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:
Charlotte Herzeel, IMEC, ExaScience Life Lab, Belgium
Damir Cavar, Eastern Michigan University, USA
Dave Herman, Mozilla Research, USA
Greg Pfeil, Clozure Associates, USA
Irène Anne Durand, LaBRI University of Bordeaux, France
Jim Newton, Cadence Design Systems, France
Kuroda Hisao, Mathematical Systems Inc., Japan
Matthew Might, University of Utah, USA
Nicolas Neuss, Friedrich Alexander Universitat, Germany
Ralf Möller, TUHH, Germany
Sam Tobin-Hochstadt, Northeastern University, USA
William Byrd, University of Utah, USA
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
_______________________________________________
Armedbear-devel mailing list
Armedbear-devel(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel
Hi,
I'm trying to use ABCL + ASDF to compile and load Maxima.
It used to work so I guess there have just been some small
changes to ABCL and/or ASDF that I need to take account of.
After (require 'asdf) and (setf asdf:*central-registry*
'(*default-pathname-defaults*)) (which wasn't necessary before,
but that doesn't matter), I find that (asdf:operate 'asdf:load-op
:maxima) fails with an error like this:
#<THREAD "interpreter" {EE920}>: Debugger invoked on condition of type
FILE-ERROR
File not found:
/home/robert/.cache/common-lisp/abcl-1.3.0-fasl42-linux-x86
/home/robert/tmp/maxima-5.33.0/src/binary-abcl/maxima-package.abcl
But maxima-package.abcl does exist in
/home/robert/tmp/maxima-5.33.0/src/binary-abcl,
and (since the current working directory is /home/robert
/tmp/maxima-5.33.0/src)
(load "binary-abcl/maxima-package.abcl") succeeds.
Then I can select option 2 (accept) and continue to the next
file, autoconf-variables.abcl, load it by hand, continue to the
next, nregex.abcl, etc etc.
/home/robert/.cache/common-lisp doesn't exist. How can I tell ASDF to
look in the same place that it actually wrote the file?
Thanks for any advice. I found some ASDF documentation
but couldn't figure it out.
best,
Robert Dodier
_______________________________________________
Armedbear-devel mailing list
Armedbear-devel(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel
;; In the test below, COMPUTE-INSIDES should be called by EXAMP-FAIL
java -jar abcl-bin-1.3.0/abcl.jar
...
CL-USER(1): (defmacro ultra-fancy-macro (&optional (x 'compute-insides))
(list 'cons ''loop (list x)))
ULTRA-FANCY-MACRO
CL-USER(2): (defun examp-fail (directives)
(labels ((compute-insides () '((here-are-the-guts)))
(compute-loop () (ultra-fancy-macro)))
(compute-loop)))
; Note: deleting unused local function LABELS COMPUTE-INSIDES
EXAMP-FAIL
CL-USER(3): (examp-fail nil) ; just checking.. maybe the Note was wrong?
(examp-fail nil)
#<THREAD "interpreter" {652D03DC}>:
Debugger invoked on condition of type UNDEFINED-FUNCTION
The function COMPUTE-INSIDES is undefined.
Restarts:
...
3: TOP-LEVEL Return to top level.
[1] CL-USER(4): 3
CL-USER(5): (defun examp-works (directives)
(labels ((compute-insides () '((here-are-the-guts)))
(compute-loop () (ultra-fancy-macro)))
#'compute-insides ; spuriously reference it
(compute-loop)))
EXAMP-WORKS
CL-USER(6): (examp-works nil)
(LOOP (HERE-ARE-THE-GUTS))
Without a statically observable use of compute-insides it is considered unused.
Macros have expanded *before* deciding that.
It is clear that the macro expands correctly based on 'examp-works'
_______________________________________________
Armedbear-devel mailing list
Armedbear-devel(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel
Hi,
There seems to be some issues loading java dependencies on OpenBSD.
I got following when trying to load hunchentoot system from quicklisp.
[1] CL-USER(7): (ql:quickload 'hunchentoot)
To load "hunchentoot":
Load 1 ASDF system:
hunchentoot
; Loading "hunchentoot"
..............
Using probed value of abcl-contrib:
'/usr/local/abcl/abcl-contrib.jar'.
Added jar:file:/usr/local/abcl/abcl-contrib.jar!/quicklisp/ to ASDF.
Added jar:file:/usr/local/abcl/abcl-contrib.jar!/mvn/ to ASDF.
Added jar:file:/usr/local/abcl/abcl-contrib.jar!/jss/ to ASDF.
Added jar:file:/usr/local/abcl/abcl-contrib.jar!/jfli/ to ASDF.
Added jar:file:/usr/local/abcl/abcl-contrib.jar!/asdf-jar/ to ASDF.
Added jar:file:/usr/local/abcl/abcl-contrib.jar!/asdf-install/ to ASDF.
Added jar:file:/usr/local/abcl/abcl-contrib.jar!/abcl-asdf/ to ASDF.
jnaASDF could not load because Java exception 'java.lang.ClassNotFoundException: AETHER.GRAPH.DEPENDENCY'..
#<THREAD "interpreter" {435DFB5F}>: Debugger invoked on condition of type JAVA-EXCEPTION
Java exception 'java.lang.ClassNotFoundException: AETHER.GRAPH.DEPENDENCY'.
Restarts:
0: ABORT Return to debug level 1.
1: RETRY Retry compiling #<ASDF/INTERFACE:MVN "jna" "net.java.dev.jna/jna/4.0.0">.
2: ACCEPT Continue, treating compiling #<ASDF/INTERFACE:MVN "jna" "net.java.dev.jna/jna/4.0.0"> as having been successful.
3: RETRY Retry compiling #<ASDF/LISP-ACTION:CL-SOURCE-FILE "cffi" "src" "cffi-abcl">.
4: ACCEPT Continue, treating compiling #<ASDF/LISP-ACTION:CL-SOURCE-FILE "cffi" "src" "cffi-abcl"> as having been successful.
5: ABORT Give up on "hunchentoot"
6: ABORT Give up on "asdf-test"
7: TOP-LEVEL Return to top level.
[2] CL-USER(8):
Here's some package version info:
abcl-1.3.0
zmyrgel:13280$ ls -l /usr/local/abcl/
total 20788
-r--r--r-- 1 root bin 75337 Mar 16 18:15 abcl-contrib.jar
-r--r--r-- 1 root bin 10414020 Mar 16 18:15 abcl.jar
-r--r--r-- 1 root bin 128156 Mar 16 18:15 abcl_completions
drwxr-xr-x 4 root wheel 512 Apr 26 18:50 src/
zmyrgel:13279$ mvn --version
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T19:37:52+02:00)
Maven home: /usr/local/maven
Java version: 1.7.0_21, vendor: Oracle Corporation
Java home: /usr/local/jdk-1.7.0/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "openbsd", version: "5.5", arch: "amd64", family: "unix"
I had little debugging help via irc but that didn't lead to any results and I've
already forgot the steps tried.
So here's an another attempt to solve this and hopefully get this resolved.
Any ideas what to try to get this resolved?
Timo
_______________________________________________
Armedbear-devel mailing list
Armedbear-devel(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel
Hi,
There seems to be some issues loading java dependencies on OpenBSD.
I got following when trying to load hunchentoot system from quicklisp.
[1] CL-USER(7): (ql:quickload 'hunchentoot)
To load "hunchentoot":
Load 1 ASDF system:
hunchentoot
; Loading "hunchentoot"
..............
Using probed value of abcl-contrib:
'/usr/local/abcl/abcl-contrib.jar'.
Added jar:file:/usr/local/abcl/abcl-contrib.jar!/quicklisp/ to ASDF.
Added jar:file:/usr/local/abcl/abcl-contrib.jar!/mvn/ to ASDF.
Added jar:file:/usr/local/abcl/abcl-contrib.jar!/jss/ to ASDF.
Added jar:file:/usr/local/abcl/abcl-contrib.jar!/jfli/ to ASDF.
Added jar:file:/usr/local/abcl/abcl-contrib.jar!/asdf-jar/ to ASDF.
Added jar:file:/usr/local/abcl/abcl-contrib.jar!/asdf-install/ to ASDF.
Added jar:file:/usr/local/abcl/abcl-contrib.jar!/abcl-asdf/ to ASDF.
jnaASDF could not load because Java exception 'java.lang.ClassNotFoundException: AETHER.GRAPH.DEPENDENCY'..
#<THREAD "interpreter" {435DFB5F}>: Debugger invoked on condition of type JAVA-EXCEPTION
Java exception 'java.lang.ClassNotFoundException: AETHER.GRAPH.DEPENDENCY'.
Restarts:
0: ABORT Return to debug level 1.
1: RETRY Retry compiling #<ASDF/INTERFACE:MVN "jna" "net.java.dev.jna/jna/4.0.0">.
2: ACCEPT Continue, treating compiling #<ASDF/INTERFACE:MVN "jna" "net.java.dev.jna/jna/4.0.0"> as having been successful.
3: RETRY Retry compiling #<ASDF/LISP-ACTION:CL-SOURCE-FILE "cffi" "src" "cffi-abcl">.
4: ACCEPT Continue, treating compiling #<ASDF/LISP-ACTION:CL-SOURCE-FILE "cffi" "src" "cffi-abcl"> as having been successful.
5: ABORT Give up on "hunchentoot"
6: ABORT Give up on "asdf-test"
7: TOP-LEVEL Return to top level.
[2] CL-USER(8):
Here's some package version info:
abcl-1.3.0
zmyrgel:13280$ ls -l /usr/local/abcl/
total 20788
-r--r--r-- 1 root bin 75337 Mar 16 18:15 abcl-contrib.jar
-r--r--r-- 1 root bin 10414020 Mar 16 18:15 abcl.jar
-r--r--r-- 1 root bin 128156 Mar 16 18:15 abcl_completions
drwxr-xr-x 4 root wheel 512 Apr 26 18:50 src/
zmyrgel:13279$ mvn --version
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T19:37:52+02:00)
Maven home: /usr/local/maven
Java version: 1.7.0_21, vendor: Oracle Corporation
Java home: /usr/local/jdk-1.7.0/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "openbsd", version: "5.5", arch: "amd64", family: "unix"
I had little debugging help via irc but that didn't lead to any results and I've
already forgot the steps tried.
So here's an another attempt to solve this and hopefully get this resolved.
Any ideas what to try to get this resolved?
Timo
_______________________________________________
Armedbear-devel mailing list
Armedbear-devel(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel
After some flailing around, I managed to figure out how to load
Maxima via ASDF + ABCL. For the record, ASDF 3.1.0.103 + ABCL 1.3.1.
The problem I reported about ASDF not looking in the right place for
the .abcl files might be due to the maxima.asd specifying a place
without telling ASDF (?? not sure). By disabling ASDF's output
translation stuff, the problem went away. Alternatively, one could
nuke the assignment to ASDF:*BINARY-OUTPUT-DIR* in maxima.asd and
let ASDF figure out where to put stuff (somewhere below ~/.cache/
common-lisp, it appears).
It appears to be necessary now to specify something for
ASDF:*CENTRAL-REPOSITORY*. I hadn't found that necessary before.
(Last time I tried might have been a couple of years ago.)
So with maxima-5.33.0.tar.gz unpacked, this recipe worked for me:
(0) cd maxima-5.33.0/src
(1) edit maxima.asd to say binary-abcl instead of binary-ecl
for ASDF:*BINARY-OUTPUT-DIR*. (Not strictly necessary.)
ASDF thens writes stuff into ./binary-abcl.
(2) launch ABCL via: java -jar path/to/abcl.jar
(3) in ABCL repl:
(require 'asdf)
(setf asdf:*central-registry* '(*default-pathname-defaults*))
(asdf:disable-output-translations)
(asdf:operate 'asdf:load-op :maxima)
(4) launch Maxima interpreter: (cl-user::run)
Plotting, help, run_testsuite all work as expected;
test suite has a few unexpected errors, mostly numerical.
FWIW
Robert Dodier
_______________________________________________
Armedbear-devel mailing list
Armedbear-devel(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel
With [r14694][], we now convert CL:T and CL:NIL to JAVA:+TRUE+ and JAVA:+FALSE+
respectively when invoking JVM methods through the JAVA package, establishing
the "natural" equivalence for boolean truth values. This may break some
existing usage in that previously CL:NIL was converted to a Java 'null'
reference. Users now need to specify JAVA:+NULL+ explicitly when desiring to
pass 'null' Java references as an argument in invoking JVM methods.
As far as I can tell from what I can from testing examples of available
consumers of the JAVA package, this doesn’t break existing usage, as we have
been advising use JAVA:+NULL+ to denote a null reference explicitly since its
introduction some three years ago [r13359][]. And until I inspected the
underlying JAVA code yesterday, I wasn’t even aware of the conversion of CL:NIL
to JAVA:+NULL+.
Nevertheless, please speak up if this breaks something for you that you relied
upon. Unless I hear otherwise, I am going to back port this change to
abcl-1.3.1 as the last change before a release. While strictly speaking from
a release engineering perspective, this sort of change should wait until a
major revision release, I am planning on using abcl-1.3.1 in production next
week with [lsw2][], which sort of relies on this behavior. I beg the ABCL
community’s indulgence in this deviation from release engineering best
practices, unless somebody speaks up soon that this is a very bad idea.
This change implements the requests in [ticket-84][] and [ticket-339][].
[ticket-84]: http://abcl.org/trac/ticket/84>
[ticket-339]: http://abcl.org/trac/ticket/339
[r14694]: http://abcl.org/trac/changeset/14694
[r13359]: http://abcl.org/trac/changeset/13359
[lsw2]: https://code.google.com/p/lsw2/
--
"A screaming comes across the sky. It has happened before but there is nothing
to compare to it now."
_______________________________________________
Armedbear-devel mailing list
Armedbear-devel(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel
Hello list,
I was wondering whether anyone has tried to get ABCL running on iOS by means of RoboVM [1]? I see that people have done this with Clojure [2]. Also, can I ask how the Android build target is coming along?
I'm weighing up LambdaNative [3] vs. alternatives for Lisp development on iOS and Android.
Cheers,
John :^P
[1] http://www.robovm.org/
[2] https://github.com/oakes/lein-fruit
[3] http://www.lambdanative.org/
--
John Pallister
john(a)johnp.net
john(a)synchromesh.com
_______________________________________________
Armedbear-devel mailing list
Armedbear-devel(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel
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
In cooperation with: ACM SIGPLAN
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. The
conference proceedings will be published in the ACM Digital Library.
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:
Charlotte Herzeel, IMEC, ExaScience Life Lab, Belgium
Damir Cavar, Eastern Michigan University, USA
Dave Herman, Mozilla Research, USA
Greg Pfeil, Clozure Associates, USA
Irène Anne Durand, LaBRI University of Bordeaux, France
Jim Newton, Cadence Design Systems, France
Kuroda Hisao, Mathematical Systems Inc., Japan
Matthew Might, University of Utah, USA
Nicolas Neuss, Friedrich Alexander Universitat, Germany
Ralf Möller, TUHH, Germany
Sam Tobin-Hochstadt, Northeastern University, USA
William Byrd, University of Utah, USA
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
_______________________________________________
Armedbear-devel mailing list
Armedbear-devel(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel
Hello,
(defun foo ()
(symbol-macrolet ((x 3))
(symbol-macrolet ((y (nth-value 0 x)))
y)))
Compiling this with COMPILE (C-c-c in slime) warns about X being
undefined, and an unbound X error occurs when FOO is run.
(macroexpand-1
'(defun foo ()
(symbol-macrolet ((x 3))
(symbol-macrolet ((y (nth-value 0 x)))
y))))
;;=>
(PROG1 (SYSTEM:%DEFUN
'FOO
(SYSTEM:NAMED-LAMBDA FOO NIL
(BLOCK FOO
(LOCALLY (LOCALLY (NTH-VALUE 0 X)))))))
X didn't get expanded.
There is no problem when compiling the DEFUN form with COMPILE-FILE (C-c-k).
_______________________________________________
Armedbear-devel mailing list
Armedbear-devel(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel