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

[armedbear-devel] Cannot get abcl 1.0.1 working with slime
by Arnaud Bailly 06 Apr '12

06 Apr '12

Hello, I am trying to use ABCL 1.0.1 with slime under emacs and get the following errors: (progn (load "/usr/share/common-lisp/source/slime/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init")) (funcall (read-from-string "swank:start-server") "/tmp/slime.3985" :coding-system "iso-latin-1-unix")) Armed Bear Common Lisp 1.0.1-svn-13750-13751 Java 1.6.0_26 Sun Microsystems Inc. Java HotSpot(TM) 64-Bit Server VM Low-level initialization completed in 0.297 seconds. Startup completed in 0.935 seconds. Type ":help" for a list of available commands. CL-USER(1): ; Loading /usr/share/common-lisp/source/slime/swank-loader.lisp ... Error loading /usr/share/common-lisp/source/slime/swank-loader.lisp at line 143 (offset 5611) #<THREAD "interpreter" {33E136A8}>: Debugger invoked on condition of type READER-ERROR The package "ASDF" can't be found. Restarts: 0: TOP-LEVEL Return to top level. [1] SWANK-LOADER(2): Here is my .emacs: (add-to-list 'load-path "/usr/share/emacs/site-lisp/slime") ;;(setq inferior-lisp-program "/usr/local/bin/sbcl") (setq inferior-lisp-program "java -cp /home/arnaud/soft/abcl-bin-1.0.1/abcl-contrib.jar -jar /home/arnaud/soft/abcl-bin-1.0.1/abcl.jar") ;; from http://functionalrants.wordpress.com/2008/09/06/how-to-set-up-emacs-slime-s… (require 'slime) (slime-setup '(slime-fancy)) Help greatly appreciated. Thanks Arnaud

3 3

[armedbear-devel] Calling java from lisp
by Arnaud Bailly 06 Apr '12

06 Apr '12

Hello (again), I am trying to invoke java code from lisp code following http://common-lisp.net/project/armedbear/doc/abcl-user.html. Here is the code I am trying to run: CL-USER> (defun java-format (fmtstring &rest args) (let* ((string-class (jclass "java.lang.String")) (array-of-objs (jclass "[Ljava.lang.Object;")) (method (jmethod string-class "format" string-class array-of-objs))) (jcall method fmtstring args))) JAVA-FORMAT And here is what I got when I try to run it: > (java-format "" "%d %08.d %s" 1 2 3) Wrong number of arguments for public static java.lang.String java.lang.String.format(java.lang.String,java.lang.Object[]): expected 2, got 1 [Condition of type PROGRAM-ERROR] Restarts: 0: [RETRY] Retry SLIME REPL evaluation request. 1: [*ABORT] Return to SLIME's top level. 2: [ABORT] Abort thread. Backtrace: 0: (#<FUNCTION {53C470B}> #<PROGRAM-ERROR {76F2D004}> #<FUNCTION {53C470B}>) 1: (APPLY #<FUNCTION {53C470B}> (#<PROGRAM-ERROR {76F2D004}> #<FUNCTION {53C470B}>)) 2: (SYSTEM::RUN-HOOK SYSTEM::*INVOKE-DEBUGGER-HOOK* #<PROGRAM-ERROR {76F2D004}> #<FUNCTION {53C470B}>) 3: (INVOKE-DEBUGGER #<PROGRAM-ERROR {76F2D004}>) 4: org.armedbear.lisp.Lisp.error(Lisp.java:381) 5: org.armedbear.lisp.Java.jcall(Java.java:880) 6: org.armedbear.lisp.Java$pf_jcall.execute(Java.java:755) 7: org.armedbear.lisp.Primitive.execute(Primitive.java:135) 8: (JCALL #<java.lang.reflect.Method public static java.lang.String j.... {451CF2D}> "" ("%d %08.d %s" 1 2 3)) 9: (JAVA-FORMAT "" "%d %08.d %s" 1 2 3) 10: (SYSTEM::%EVAL (JAVA-FORMAT "" "%d %08.d %s" 1 2 3)) 11: (EVAL (JAVA-FORMAT "" "%d %08.d %s" 1 2 3)) --more-- What am I doing wrong ? Arnaud

2 2

Re: [armedbear-devel] run-program :environment nil
by Ville Voutilainen 31 Mar '12

31 Mar '12

On 29 March 2012 17:15, Rudolf Schlatte <rudi(a)ifi.uio.no> wrote: > asdf doesn't use run-program for abcl, just run-shell-command. But I see your point about API changes, especially for a non-major release. I guess right now we're bike-shedding. Let's hear what Pascal prefers, but I'm leaning towards your version as well at the moment. I'm not hell-bent on it, just wanted to point that out since I did consider that even though my patch doesn't mention such considerations. Ville-code is sometimes like that, it's well thought-out and minimal, modify anything and things break (for certain values of "break"), but I'm not the best user of explanatory comments on the planet. :)

1 1

Re: [armedbear-devel] run-program :environment nil
by Ville Voutilainen 29 Mar '12

29 Mar '12

Forwarding my reply to the list too. :) On 29 March 2012 16:55, Ville Voutilainen <ville.voutilainen(a)gmail.com> wrote: > On 29 March 2012 16:41, Rudi Schlatte <rudi(a)ifi.uio.no> wrote: >> Ville Voutilainen <ville.voutilainen(a)gmail.com> writes: >>> Here's a tentative patch. I opted for a new keyword argument, since >>> the new function approach would've led to duplication or to a macro >>> that has the new argument anyway. Untested so far, so this is for >>> general review. Also lacking the docstring changes. >> Here's my version, using your getenv and process-builder changes. I >> get by with only the :environment key, see the docstring for an example >> on how to overwrite PATH and keep the rest. Lightly tested. > > Looks reasonable. Some questions though: > >> -(defun run-program (program args &key environment (wait t)) >> +(defun run-program (program args &key (environment nil environment-p) (wait t)) > > Ah, yes, this works too, no need for a separate clear-env. But, does > this change the > semantics? Our previous code did an environment-merge if an > environment is supplied. > This one will clear and insert, and requires using getenv-all if you > want to replace > only some parts. I don't want to do such a semantics change. By > avoiding the semantics > change, I don't need to worry about breaking asdf. > > For that point, I'm still biased towards the clear-env keyword arg > approach. In that > approach, getenv-all is just an utility function that you can use if > you want to do > weird-complex environment processing, but possibly the most common use cases are > still "replace a couple of values by providing an environment without > clearing" and > "run in a very restricted environment with only a handful of > variables", neither of > which requires the use of getenv-all. > > Comments?

1 0

Re: [armedbear-devel] run-program :environment nil
by Rudi Schlatte 29 Mar '12

29 Mar '12

[Originally sent to Ville only because of a disagreement between Gnus and me]

1 0

[armedbear-devel] run-program :environment nil
by Pascal J. Bourguignon 29 Mar '12

29 Mar '12

(lisp-implementation-version) --> "1.0.1" The documentation of extensions:run-program is misleading: :environment An alist of STRINGs (name . value) describing the new environment. The default is to copy the environment of the current process. The alist doesn't describe the NEW environment, it is only MERGED into the current environment. Now of course, I consider the current behavior to be a bug: (text-stream-contents (extensions:process-output (extensions:run-program "env" '() :wait t :environment 'nil))) --> ("NNTPSERVER=news.individual.net" "ESHELL=/bin/bash" …) I would expect: (text-stream-contents (extensions:process-output (extensions:run-program "env" '() :wait t :environment 'nil))) --> () and: (text-stream-contents (extensions:process-output (extensions:run-program "env" '() :wait t :environment '(("LC_CTYPE" . "C"))))) --> ("LC_CTYPE=C")) Which would match what the documentation says. Also, in a shell environment, an empty variable is not the same as an inexistant variable, so I cannot just loop over all the existing variables to set them to an empty string. I see no SYSTEM::%PROCESS-BUILDER-ENV-REM function… -- __Pascal Bourguignon__ http://www.informatimago.com/ A bad day in () is better than a good day in {}.

4 8

[armedbear-devel] ABCL on jdk-1.7.0_03
by Mark Evenson 21 Mar '12

21 Mar '12

I've just run abcl-1.1.0-dev the ANSI-COMPILED tests on jdk-1.7.0_03 with reasonable looking results of 31 failures, which is roughly the same number as those run with jdk-1.6.0_31 (some of the tests use randomly generated data so they sometimes either fail or succeed). Previously, I think that we weren't even completing the ANSI-COMPILED test suite due to issues in the character set encoding, so I think we should now more fully endorse running ABCL on Java7.

1 0

[armedbear-devel] compiled errors: debug.assertTrue()
by scarbonell＠ono.com 06 Mar '12

06 Mar '12

Hi, When I try to compile the mcs-core.cl file (attached) with java abcl, I get this error: Failed to get InputStream for 'jar:file:D:/otro/kernel/modules/fmcs.bin!/mcs_core_4.cls'ABCL Debug.assertTrue() assertion failed!java.lang.Error: ABCL Debug.assertTrue() assertion failed! Why is this happening? How can I resolved it? Thanks

3 3

[armedbear-devel] compiling lisp files outside Java and calling it after with abcl
by scarbonell＠ono.com 02 Mar '12

02 Mar '12

Hi,I'm trying to compile a lisp application and I get a lot of errors with java abcl. I thought that if I try to compile this lisp files outside of abcl with other systems, perhaps, I could then call this compiled functions lisp files from ABCL (look like a jar file of lisp compiled files). Is this possible?How can I compiled this files outside ABCL? Some examples?Thanks

5 10

[armedbear-devel] Upcoming abcl-1.1 branch
by Mark Evenson 25 Feb '12

25 Feb '12

On [#abcl]() yesterday, ehu and easye discussed how it would be a good idea to start packing up for shipping abcl-1.1 out the door. [#abcl]: http://webchat.freenode.net/?randomnick=1&channels=abcl&prompt=1&uio=d4 Out of our brief discussion, we'd like to branch the trunk in about a week, stabilize with testing, and then release abcl-1.1.0 on 14-FEB-2012. So, unless there are objections, we'd like to start by asking everyone who was thinking of patching something, to think about getting some time in the next week to get something done. All potential contributions are welcome. If you were going to document something, now's the time! [Rudi added real BibTex-based markup to the Manual][1], so even something as trivial as fixing the references would be appreciated. [1]: http://code.google.com/p/abcl-dynamic-install/source/detail?r=5c7faeeb35408… yers in CONS, Mark -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."

2 2