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

[armedbear-devel] Figuring out the provenance of trunk
by Mark Evenson 11 Jun '12

11 Jun '12

Over the course of maintaining the Bear, it has become clear to me that we have pieces of code in trunk whose original licensing terms indicate that their author should be contacted as to their status, especially when they would conflict with the terms we distribute under, namely those of the GNU Public License. Recently I discovered such a licensing lacunae [in working with Jorge Tavares to patch the CL:SORT and CL:STABLE-SORT routines][1], that 'sort.lisp' contains code that has both SBCL and ECL code attributions. Are we in violation of anything here? Dunno. But we certainly have *lots* of SBCL tucked into our tree… We obviously need an estimate of our non-compliance. As a first step, it seems useful to construct/use a tool that allows us to establish provenance of all commits to ABCL trunk. With this history in hand, we can start figuring out the set of all authors to work through potential conflicts. A fair amount of work for a non-specialist, but anyone who does this regularly should have an analysis toolset lying around that they could apply to [ABCL trunk][2]. Is there a language lawyer geek in the house? [1]: http://trac.common-lisp.net/armedbear/ticket/196 [2]: https://code.google.com/p/abcl-dynamic-install/source/browse/ -- "A screaming comes across the sky. It has happened before, but there is nothing to compare it to now."

3 3

[armedbear-devel] Patch to quicklisp/cffi-0.7.1 for abcl-1.1.0-dev
by Mark Evenson 30 May '12

30 May '12

Mebbe [this can help somewhat with the problems loading JNA automatically for CFFI on ABCL][1]. I still need to figure out exactly what is broken under which JVM/OS combinations. Interesting stuff in analyzing regressions. [1]: http://slack.net/~evenson/quicklisp/cffi-abcl-1.1.0-dev-20120530a.patch -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."

1 0

[armedbear-devel] Is anybody interested in jfli-abcl?
by Alex Mizrahi 29 May '12

29 May '12

jfli-abcl, basically, allows one to quickly create Lisp function wrappers for Java classes. E.g. (def-java-class "java.sql.DriverManager") (use-package :|java.sql|) (DriverManager.getConnection ...) The benefit over java:jcall and JSS is that it looks more-or-less like normal Lisp function calls, pretty similar to a wrapper you could write yourself. Also, potentially, it might carry less runtime overhead because everything can be resolved at compile-time. And if you use SLIME, auto-completion works. It doesn't like mixed case, though, so you need to write it like (|java.sql|:drivermanager.getcollection ...) Still, better than nothing. As far as I can tell, jfli-abcl isn't currently maintained. But as I'm used to jfli-abcl I maintain my own version with some fixes. If there is any interest in jfli-abcl I could, perhaps,. publish my version and polish it a bit. (I'm personally not interested in new-class functionality which allows one to create Java class from Lisp.) (I've found this updated version: https://gist.github.com/avodonosov/abcl-idea/blob/master/src/abclidea/lisp/… But haven't yet checked if it works with latest ABCL and what are improvements against old one.)

6 11

[armedbear-devel] Fwd: Is anybody interested in jfli-abcl?
by Anton Vodonosov 28 May '12

28 May '12

[forwarding Alessio's reply to the list - was my mistake to send the previous letter to him directly, instead of Reply All] ----------------------------------------------------------------------------------------------------- 28.05.2012, 17:25, "Alessio Stalla" <alessiostalla(a)gmail.com>: On Mon, May 28, 2012 at 3:18 PM, Anton Vodonosov <avodonosov(a)yandex.ru> wrote: > 28.05.2012, 17:08, "Alessio Stalla" <alessiostalla(a)gmail.com>: >> On Mon, May 28, 2012 at 2:57 PM, Anton Vodonosov <avodonosov(a)yandex.ru> wrote: >>> 28.05.2012, 16:22, "Anton Vodonosov" <avodonosov(a)yandex.ru>: >>>> If independent version of new-class is not ready, probably it's possible to >>>> deliver runtime-class a a contrib [...] >>> I've checked the ABCL sources and see that runtime-class.lisp is now >>> included into ABCL. So we don't even need to create a contrib for it. >>> >>> Could anyone help me understand the problem with new-class, why removing >>> it? Namely, when the asm.jar will be needed, >>> >>> What I understand now: >>> >>> 1. abcl-jfli function jrc calls java:jnew-runtime-class. >>> 2. java:jnew-runtime-class needs asm.jar. >> 2. is wrong. jnew-runtime-class used to require asm, was disabled, and >> was reintroduced (incomplete) without a dependency to asm and with a >> slightly different API. In other words, jrc right now is probably >> broken. >> >> To restore jrc right now, you'd need to restore runtime-class.lisp >> from version control, and bundle it in contrib under a different >> package (assuming it still works with present-day asm). > Ah I see, it's different runtime-class. Thanks for the explanation. >> That would be possible, but I object that having 2 different APIs for >> the same thing is a potential source for confusion. > Yes, but it's also the way of software evolution: we use some API, > notice it's deficiencies, deprecate it and introduce new, better > API. Let me note that it could have been called runtime-class2 > to avoid confusion and compatibility issues. Yes, maybe it could, but the situation as I saw it was that runtime-class was effectively dead code nobody was using (and in fact, until now nobody asked about it on this list). > Probably now, if packaging the old runtime-class as a contrib, we will > need to rename it to old-runtime-class, or even deprecated-runtime-class. Or just deprecated:runtime-class, or backwards-compatibility:..., so you can shadowing-import-from it and forget about it. > Could you explain about the asm.jar dependency in case of the > deprecated-runtime-class? Would it be a load-time dependency, > or a call-time dependency? IIRC, it is a call-time dependency, but note that I never used the old runtime-class, so I may be wrong. Alessio -- Some gratuitous spam: http://ripple-project.org Ripple, social credit system http://villages.cc Villages.cc, Ripple-powered community economy http://common-lisp.net/project/armedbear ABCL, Common Lisp on the JVM http://code.google.com/p/tapulli my current open source projects http://www.manydesigns.com/ ManyDesigns Portofino, open source model-driven Java web application framework

1 1

[armedbear-devel] Fwd: Is anybody interested in jfli-abcl?
by Anton Vodonosov 28 May '12

28 May '12

28.05.2012, 17:08, "Alessio Stalla" <alessiostalla(a)gmail.com>: > On Mon, May 28, 2012 at 2:57 PM, Anton Vodonosov <avodonosov(a)yandex.ru> wrote: >> 28.05.2012, 16:22, "Anton Vodonosov" <avodonosov(a)yandex.ru>: >>> If independent version of new-class is not ready, probably it's possible to >>> deliver runtime-class a a contrib [...] >> I've checked the ABCL sources and see that runtime-class.lisp is now >> included into ABCL. So we don't even need to create a contrib for it. >> >> Could anyone help me understand the problem with new-class, why removing >> it? Namely, when the asm.jar will be needed, >> >> What I understand now: >> >> 1. abcl-jfli function jrc calls java:jnew-runtime-class. >> 2. java:jnew-runtime-class needs asm.jar. > 2. is wrong. jnew-runtime-class used to require asm, was disabled, and > was reintroduced (incomplete) without a dependency to asm and with a > slightly different API. In other words, jrc right now is probably > broken. > > To restore jrc right now, you'd need to restore runtime-class.lisp > from version control, and bundle it in contrib under a different > package (assuming it still works with present-day asm). Ah I see, it's different runtime-class. Thanks for the explanation. > That would be possible, but I object that having 2 different APIs for > the same thing is a potential source for confusion. Yes, but it's also the way of software evolution: we use some API, notice it's deficiencies, deprecate it and introduce new, better API. Let me note that it could have been called runtime-class2 to avoid confusion and compatibility issues. Probably now, if packaging the old runtime-class as a contrib, we will need to rename it to old-runtime-class, or even deprecated-runtime-class. Could you explain about the asm.jar dependency in case of the deprecated-runtime-class? Would it be a load-time dependency, or a call-time dependency? Best regards, - Anton

1 0

[armedbear-devel] abcl trunk build doesn't work for me
by Alex Mizrahi 27 May '12

27 May '12

hi When I run ABCL built from trunk I get this error when I run it: ---- Armed Bear Common Lisp 1.1.0-dev Java 1.6.0_21 Sun Microsystems Inc. OpenJDK 64-Bit Server VM Low-level initialization completed in 1.072 seconds. org.armedbear.lisp.IntegrityError at org.armedbear.lisp.Primitives$pf_error.execute(Primitives.java:1577) at org.armedbear.lisp.Primitive.execute(Primitive.java:113) at org.armedbear.lisp.Symbol.execute(Symbol.java:802) at org.armedbear.lisp.Lisp.error(Lisp.java:380) at org.armedbear.lisp.Load.loadSystemFile(Load.java:276) at org.armedbear.lisp.Load$load_system_file.execute(Load.java:703) at org.armedbear.lisp.LispThread.execute(LispThread.java:649) at org.armedbear.lisp.Lisp.evalCall(Lisp.java:550) at org.armedbear.lisp.Lisp.eval(Lisp.java:515) at org.armedbear.lisp.Load.loadStream(Load.java:570) at org.armedbear.lisp.Load.loadFileFromStream(Load.java:538) at org.armedbear.lisp.Load.loadFileFromStream(Load.java:428) at org.armedbear.lisp.Load.loadSystemFile(Load.java:327) at org.armedbear.lisp.Interpreter.initializeLisp(Interpreter.java:172) at org.armedbear.lisp.Interpreter.createDefaultInstance(Interpreter.java:102) at org.armedbear.lisp.Main$1.run(Main.java:46) at java.lang.Thread.run(Thread.java:679) ERROR placeholder called with arguments: Failed to find loadable system file 'autoloads' in boot classpath. ---- I tried both version from SVN and from Mark's (?) hg repo, upgraded OpenJDK to 1.6.0_21, upgraded ant from 1.7.1 to 1.8.0 (that's top version I can get via package manager for Ubuntu 10.04). I was able to build and run ABCL 1.0.1. I noticed a bug on abcl 1.0.1: in certain rather contrived code return-from was ignored, i.e. evaluation continued as if it wasn't called. And was going to check whether it's present in the latest devel version before investigating it further.

4 7

[armedbear-devel] Connection to database via JDBC and classpath
by Francisco Vides Fernández 24 May '12

24 May '12

Hello everyone I intend to use ABCL in one of my projects. I've started to connectiing to a postgresq database via jdbc. I've tried something like: -------8<------- (add-to-classpath (merge-pathnames #p".m2/repository/postgresql/postgresql/8.4-702.jdbc4/postgresql-8.4-702.jdbc4.jar" (user-homedir-pathname))) (jstatic "forName" "java.lang.Class" "org.postgresql.Driver") -------8<------- But it always returns -------8<------- Java exception 'java.lang.ClassNotFoundException: org.postgresql.Driver'. [Condition of type JAVA-EXCEPTION] -------8<------- The jar file exists, and has the proper class inside. I've read the manual, and googled a bit, but still get the same error. I'm using Ubuntu Linux, with OpenJDK 1.6.0_24, and the latest and greatest ABCL downloaded as a binary from ABCL website. Can someone point me what I'm doing wrong? Many thanks for this great project!! -- +----------------- | Francisco Vides Fernández <fvides(a)neoclinic.es> | Director Ejecutivo | Teléfono fijo: 952 60 29 59 | Fax: 952 60 29 59 | Neoclinic http://www.neoclinic.es/ +------

6 13

[armedbear-devel] ABCL has an incorrect belief about hostname and cpu in its fasl storage
by Paul Nathan 18 May '12

18 May '12

Dear all, I installed Armed Bear Common Lisp 1.0.1-svn-13750-13751 in order to run it on my OSX 10.6 (Snow Leopard) 64-bit system (Darwin 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun 7 16:32:41 PDT 2011; root:xnu-1504.15.3~1/RELEASE_X86_64 x86_64), for the purpose of executing cl-test-grid. However, I observed that the fasls were being stored in ~/.cache/common-lisp/abcl-1.0.1-svn-13750-13751-fasl38-solaris-x86 You will quickly note that my system is neither solaris nor x86. However, I checked some of the environment settings: java -jar abcl.jar Armed Bear Common Lisp 1.0.1-svn-13750-13751 Java 1.6.0_31 Apple Inc. Java HotSpot(TM) 64-Bit Server VM Low-level initialization completed in 0.619 seconds. Startup completed in 1.511 seconds. Type ":help" for a list of available commands. CL-USER(1): *features* (:JAVA-1.6 :ARMEDBEAR :ABCL :COMMON-LISP :ANSI-CL :UNIX :DARWIN :CDR6) CL-USER(2): (machine-instance) "elendil.local" CL-USER(3): (machine-type) "X86_64" CL-USER(4): (software-type) "Mac OS X" CL-USER(5): (software-version) "10.6.8" CL-USER(6): (machine-version) NIL And they turn out correct. I am not a regular ABCL user, so pardon me if this is already known. If an OSX Snow Leopard system is not available for testing, I volunteer my time and machine to test a patch. Regards, Paul Nathan

2 2

[armedbear-devel] One (probably) stupid question
by Francisco Vides Fernández 18 May '12

18 May '12

I'm aware that this must be a stupid question, but after googling for a while can't find the right answer: How can I invoke a method with a boolean as an argument. I try to do the following: ---8<--- (let* ((jlclass (jclass "java.lang.Class")) (for-name (jmethod jlclass "forName" (jclass "java.lang.String") (jclass "boolean") (jclass "java.lang.ClassLoader")))) (jstatic for-name jlclass "org.postgresql.Driver" t (get-current-classloader))) ---8<--- But it raises the error: The value T is not of class boolean [Condition of type ERROR] I tried replacing '(jclass "boolean") for '(jclass "java.lang.Boolean"), but in that case it doesn't find the for-name method. How am I supposed to invoke the method! Thanks in advance! -- +----------------- | Francisco Vides Fernández <fvides(a)dedaloingenieros.com> | Gerente | Teléfono fijo: 952 60 29 59 | Fax: 952 60 29 59 | igaleno http://www.igaleno.com/ +------

2 1

[armedbear-devel] sockets in CLISP
by Santiago Carbonell 18 May '12

18 May '12

Hi, I'm trying to send some strings using the format function in LISP to a sockets but always I obtain NIL I'm using this function: (defun sockets_fun() (WITH-OPEN-STREAM (socket (SOCKET:SOCKET-CONNECT 49729 "localhost")) (let ((*standard-output* socket)) (format socket "The color is ~A" "red") (force-output socket) (finish-output nil) ))) But always I obtain NIL in the socket Instead of that function I've tried to use this another function: (defun geetings() (print "hi")) and works fine, appears hi in the socket Why there are problems with sockets with the format function? Thanks

2 1