armedbear-devel

armedbear-devel@common-lisp.net

2 participants
1202 discussions

Hi, problem with building ABCL extension for MIT App Inventor
by Tomislav Tomšić 26 Aug '17

26 Aug '17

Greetings, currently I am building extension for AI, as indicated in title. It works for Scheme (JScheme and Kawa). It is quite a simply one, for now, I am only interested in evaluating simple symbolic expression, and then build on that, adding other features etc. However, I would also like to have access to Common Lisp, ergo ABCL. Here is a code for its respective method: @SimpleFunction(description = "ABCL evaluation") public String ABCLEvaluation(String expression) { // Environment.getInstance(true); // Interpreter abclInterpreter = Interpreter.createInstance(); // Interpreter.createInstance(); // LispObject evalResult = Interpreter.evaluate(expression); Interpreter interpreter = Interpreter.createInstance(); LispObject lo= interpreter.eval(expression); return lo.getStringValue(); } Commented code is there for completion sake, just as an indication that I tried everything I could find in documentation and examples. Nothing works. As you see, idea is a simple one, String is received, and then evaluated, except that in the case of ABCL it isn't. For JScheme and Kawa logic is precisely the same, environment/interpreter is initialized, expression is evaluated and then it returns the correct result. After playing with the various code combinations, there are always just two errors present in logs, so here they are: First one: W/System.err(20761): java.lang.NullPointerException: Attempt to invoke virtual method 'org.armedbear.lisp.LispObject org.armedbear.lisp.Interpreter.eval(java.lang.String)' on a null object reference W/System.err(20761): at lisp.tomislavt.ext.LispEvaluation.ABCLEvaluation(LispEvaluation.java:46) W/System.err(20761): at java.lang.reflect.Method.invoke(Native Method) W/System.err(20761): at java.lang.reflect.Method.invoke(Method.java:372) W/System.err(20761): at gnu.expr.PrimProcedure.apply(PrimProcedure.java:285) W/System.err(20761): at gnu.mapping.CallContext.runUntilDone(CallContext.java:234) W/System.err(20761): at gnu.mapping.CallContext.runUntilValue(CallContext.java:298) W/System.err(20761): at gnu.mapping.MethodProc.applyN(MethodProc.java:113) W/System.err(20761): at gnu.kawa.reflect.Invoke.applyN(Invoke.java:193) W/System.err(20761): at gnu.kawa.functions.ApplyToArgs.applyN(ApplyToArgs.java:139) W/System.err(20761): at gnu.kawa.functions.Apply.applyN(Apply.java:70) W/System.err(20761): at gnu.mapping.ProcedureN.apply2(ProcedureN.java:39) W/System.err(20761): at com.google.youngandroid.runtime.callComponentMethod(runtime1661793284635134238.scm:879) W/System.err(20761): at appinventor.ai_test.AbclKawaTest.Screen1.Abcl$Click(Screen1.yail:68) W/System.err(20761): at appinventor.ai_test.AbclKawaTest.Screen1$frame.apply0(Screen1.yail:456) W/System.err(20761): at gnu.expr.ModuleBody.applyN(ModuleBody.java:226) W/System.err(20761): at gnu.expr.ModuleMethod.applyN(ModuleMethod.java:216) W/System.err(20761): at gnu.kawa.functions.ApplyToArgs.applyN(ApplyToArgs.java:139) W/System.err(20761): at gnu.kawa.functions.Apply.applyN(Apply.java:70) W/System.err(20761): at gnu.mapping.ProcedureN.apply2(ProcedureN.java:39) W/System.err(20761): at appinventor.ai_test.AbclKawaTest.Screen1.dispatchEvent(Screen1.yail:10121) W/System.err(20761): at com.google.appinventor.components.runtime.EventDispatcher.delegateDispatchEvent(EventDispatcher.java:220) W/System.err(20761): at com.google.appinventor.components.runtime.EventDispatcher.dispatchEvent(EventDispatcher.java:198) W/System.err(20761): at com.google.appinventor.components.runtime.Button.Click(Button.java:51) W/System.err(20761): at com.google.appinventor.components.runtime.Button.click(Button.java:43) W/System.err(20761): at com.google.appinventor.components.runtime.ButtonBase.onClick(ButtonBase.java:656) W/System.err(20761): at android.view.View.performClick(View.java:4848) W/System.err(20761): at android.view.View$PerformClick.run(View.java:20262) W/System.err(20761): at android.os.Handler.handleCallback(Handler.java:815) W/System.err(20761): at android.os.Handler.dispatchMessage(Handler.java:104) W/System.err(20761): at android.os.Looper.loop(Looper.java:194) W/System.err(20761): at android.app.ActivityThread.main(ActivityThread.java:5631) W/System.err(20761): at java.lang.reflect.Method.invoke(Native Method) W/System.err(20761): at java.lang.reflect.Method.invoke(Method.java:372) W/System.err(20761): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:959) W/System.err(20761): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:754) I/RuntimeErrorAlert(20761): in alert Second one: W/System.err(26401): Unable to determine LISP_HOME. W/System.err(26401): Unable to determine LISP_HOME. W/System.err(26401): org.armedbear.lisp.IntegrityError W/System.err(26401): at org.armedbear.lisp.Primitives$pf_error.execute(Primitives.java:1577) W/System.err(26401): at org.armedbear.lisp.Primitive.execute(Primitive.java:113) W/System.err(26401): at org.armedbear.lisp.Symbol.execute(Symbol.java:803) W/System.err(26401): at org.armedbear.lisp.Lisp.error(Lisp.java:383) W/System.err(26401): at org.armedbear.lisp.Load.loadSystemFile(Load.java:322) W/System.err(26401): at org.armedbear.lisp.Interpreter.initializeLisp(Interpreter.java:172) W/System.err(26401): at org.armedbear.lisp.Interpreter.createInstance(Interpreter.java:72) W/System.err(26401): at lisp.tomislavt.ext.LispEvaluation.ABCLEvaluation(LispEvaluation.java:48) W/System.err(26401): at java.lang.reflect.Method.invoke(Native Method) W/System.err(26401): at java.lang.reflect.Method.invoke(Method.java:372) W/System.err(26401): at gnu.expr.PrimProcedure.apply(PrimProcedure.java:285) W/System.err(26401): at gnu.mapping.CallContext.runUntilDone(CallContext.java:234) W/System.err(26401): at gnu.mapping.CallContext.runUntilValue(CallContext.java:298) W/System.err(26401): at gnu.mapping.MethodProc.applyN(MethodProc.java:113) W/System.err(26401): at gnu.kawa.reflect.Invoke.applyN(Invoke.java:193) W/System.err(26401): at gnu.kawa.functions.ApplyToArgs.applyN(ApplyToArgs.java:139) W/System.err(26401): at gnu.kawa.functions.Apply.applyN(Apply.java:70) W/System.err(26401): at gnu.mapping.ProcedureN.apply2(ProcedureN.java:39) W/System.err(26401): at com.google.youngandroid.runtime.callComponentMethod(runtime284371300273757224.scm:879) W/System.err(26401): at appinventor.ai_test.AbclKawaTest3.Screen1.Abcl$Click(Screen1.yail:68) W/System.err(26401): at appinventor.ai_test.AbclKawaTest3.Screen1$frame.apply0(Screen1.yail:456) W/System.err(26401): at gnu.expr.ModuleBody.applyN(ModuleBody.java:226) W/System.err(26401): at gnu.expr.ModuleMethod.applyN(ModuleMethod.java:216) W/System.err(26401): at gnu.kawa.functions.ApplyToArgs.applyN(ApplyToArgs.java:139) W/System.err(26401): at gnu.kawa.functions.Apply.applyN(Apply.java:70) W/System.err(26401): at gnu.mapping.ProcedureN.apply2(ProcedureN.java:39) W/System.err(26401): at appinventor.ai_test.AbclKawaTest3.Screen1.dispatchEvent(Screen1.yail:10121) W/System.err(26401): at com.google.appinventor.components.runtime.EventDispatcher.delegateDispatchEvent(EventDispatcher.java:220) W/System.err(26401): at com.google.appinventor.components.runtime.EventDispatcher.dispatchEvent(EventDispatcher.java:198) W/System.err(26401): at com.google.appinventor.components.runtime.Button.Click(Button.java:51) W/System.err(26401): at com.google.appinventor.components.runtime.Button.click(Button.java:43) W/System.err(26401): at com.google.appinventor.components.runtime.ButtonBase.onClick(ButtonBase.java:656) W/System.err(26401): at android.view.View.performClick(View.java:4848) W/System.err(26401): at android.view.View$PerformClick.run(View.java:20262) W/System.err(26401): at android.os.Handler.handleCallback(Handler.java:815) W/System.err(26401): at android.os.Handler.dispatchMessage(Handler.java:104) W/System.err(26401): at android.os.Looper.loop(Looper.java:194) W/System.err(26401): at android.app.ActivityThread.main(ActivityThread.java:5631) W/System.err(26401): at java.lang.reflect.Method.invoke(Native Method) W/System.err(26401): at java.lang.reflect.Method.invoke(Method.java:372) W/System.err(26401): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:959) W/System.err(26401): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:754) I/System.out(26401): ERROR placeholder called with arguments: I/System.out(26401): Failed to find loadable system file 'boot.lisp' in boot classpath. I/System.out(26401): Failed to find loadable system file 'boot.lisp' in boot classpath. W/System.err(26401): org.armedbear.lisp.IntegrityError W/System.err(26401): at org.armedbear.lisp.Primitives$pf_error.execute(Primitives.java:1577) W/System.err(26401): at org.armedbear.lisp.Primitive.execute(Primitive.java:113) W/System.err(26401): at org.armedbear.lisp.Symbol.execute(Symbol.java:803) W/System.err(26401): at org.armedbear.lisp.Lisp.error(Lisp.java:383) W/System.err(26401): at org.armedbear.lisp.Load.loadSystemFile(Load.java:322) W/System.err(26401): at org.armedbear.lisp.Interpreter.initializeLisp(Interpreter.java:172) W/System.err(26401): at org.armedbear.lisp.Interpreter.createInstance(Interpreter.java:72) W/System.err(26401): at lisp.tomislavt.ext.LispEvaluation.ABCLEvaluation(LispEvaluation.java:48) W/System.err(26401): at java.lang.reflect.Method.invoke(Native Method) W/System.err(26401): at java.lang.reflect.Method.invoke(Method.java:372) W/System.err(26401): at gnu.expr.PrimProcedure.apply(PrimProcedure.java:285) W/System.err(26401): at gnu.mapping.CallContext.runUntilDone(CallContext.java:234) W/System.err(26401): at gnu.mapping.CallContext.runUntilValue(CallContext.java:298) W/System.err(26401): at gnu.mapping.MethodProc.applyN(MethodProc.java:113) W/System.err(26401): at gnu.kawa.reflect.Invoke.applyN(Invoke.java:193) W/System.err(26401): at gnu.kawa.functions.ApplyToArgs.applyN(ApplyToArgs.java:139) W/System.err(26401): at gnu.kawa.functions.Apply.applyN(Apply.java:70) W/System.err(26401): at gnu.mapping.ProcedureN.apply2(ProcedureN.java:39) W/System.err(26401): at com.google.youngandroid.runtime.callComponentMethod(runtime284371300273757224.scm:879) W/System.err(26401): at appinventor.ai_test.AbclKawaTest3.Screen1.Abcl$Click(Screen1.yail:68) W/System.err(26401): at appinventor.ai_test.AbclKawaTest3.Screen1$frame.apply0(Screen1.yail:456) W/System.err(26401): at gnu.expr.ModuleBody.applyN(ModuleBody.java:226) W/System.err(26401): at gnu.expr.ModuleMethod.applyN(ModuleMethod.java:216) W/System.err(26401): at gnu.kawa.functions.ApplyToArgs.applyN(ApplyToArgs.java:139) W/System.err(26401): at gnu.kawa.functions.Apply.applyN(Apply.java:70) W/System.err(26401): at gnu.mapping.ProcedureN.apply2(ProcedureN.java:39) W/System.err(26401): at appinventor.ai_test.AbclKawaTest3.Screen1.dispatchEvent(Screen1.yail:10121) W/System.err(26401): at com.google.appinventor.components.runtime.EventDispatcher.delegateDispatchEvent(EventDispatcher.java:220) W/System.err(26401): at com.google.appinventor.components.runtime.EventDispatcher.dispatchEvent(EventDispatcher.java:198) W/System.err(26401): at com.google.appinventor.components.runtime.Button.Click(Button.java:51) W/System.err(26401): at com.google.appinventor.components.runtime.Button.click(Button.java:43) W/System.err(26401): at com.google.appinventor.components.runtime.ButtonBase.onClick(ButtonBase.java:656) W/System.err(26401): at android.view.View.performClick(View.java:4848) W/System.err(26401): at android.view.View$PerformClick.run(View.java:20262) W/System.err(26401): at android.os.Handler.handleCallback(Handler.java:815) W/System.err(26401): at android.os.Handler.dispatchMessage(Handler.java:104) W/System.err(26401): at android.os.Looper.loop(Looper.java:194) W/System.err(26401): at android.app.ActivityThread.main(ActivityThread.java:5631) W/System.err(26401): at java.lang.reflect.Method.invoke(Native Method) W/System.err(26401): at java.lang.reflect.Method.invoke(Method.java:372) W/System.err(26401): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:959) W/System.err(26401): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:754) I hope that I am missing something obvious :), and I am thankful in advance for any input, advice or idea. Some additional clarification may be in order, MIT App Inventor is environment for rapid development of applications for Android (Arduino, Lego mindstorm etc.), hence it doesn't follow usual Android work-flow. Backbone of it is Kawa, components, extensions are written in Java, but more about it can be easily find on its webpage. First log example is fairly useless one imo, when i tested my extension with simple App, same expression was evaluated correctly in both Kawa and JScheme, so that String was not a null one, but I've put it here for completion sake. For the second one I've find something similar for version a.1 or 1.2, back in 2012, I believe, and it was something about dynamic linking during the build process. I am using ABCL 1.5 jar that I downloaded from the ABCL project page. In any case, I am bit at loss, and thus, I would appreciate any advice what should I try next. Thank you for your time. Respectfully, Tomislav Tomsic

2 1

ASDF Issue with compiler warnings on ABCL
by Robert Goldman 18 Aug '17

18 Aug '17

ASDF wraps its compilation process with WITH-COMPILATION-UNIT. On at least some implementations, this is necessary so that building doesn't emit spurious undefined function (variable, etc.) warnings. However, on ABCL, using WITH-COMPILATION-UNIT has the side effect of causing warnings to be intercepted and handled by HANDLE-WARNING. Then it seems that *resignal-compiler-warnings* is bound to NIL, and the compiler swallows them, instead of allowing them to flow down the stack to ASDF's handlers. In turn, this causes at least some of our regression tests to fail, because they check for expected warnings. This looks to me like a bug, but perhaps it's a feature ;-) Would you please explain and let us know how to handle this? thanks, r

2 2

Directory and wild pathnames.
by Mark Cox 24 Jul '17

24 Jul '17

G'day all, The following code signals an error in ABCL 1.5.0 on OS X 10.10.5. [1] CL-USER(1): (directory (merge-pathnames (make-pathname :directory '(:relative :wild)) (user-homedir-pathname))) #<THREAD "interpreter" {590C3415}>: Debugger invoked on condition of type TYPE-ERROR The value NIL is not of type (OR PATHNAME STRING FILE-STREAM SYSTEM:JAR-STREAM SYSTEM:URL-STREAM). Any help would be appreciated. Thanks Mark Cox

2 1

Putative abcl-1.5.0 release plan
by Mark Evenson 21 Jul '17

21 Jul '17

In the "gee that took a lot longer than expected", I'd like to announce my rough plan to release abcl-1.5.0 in the next week. The biggest change in the implementation will be the dropping of Java 5 support since there is no longer a freely redistributable JDK5 implementation (it went with the Sun set…) to run the GPL'd ABCL upon. We will endeavor to ensure that Java 6 continues to be supported as long as the openjdk6 is actively maintained. As always, comments and patches solicited. Yers in CONS, Mark >From <http://abcl.org/trac/milestone/1.5.0>: Milestones ========== Drop Java 5; ensure Java [678] work well. ABCL-CONTRIB ------------ ABCL-BUILD Unified build system (using UIOP; able to install and use Ant, Maven, and others via interactive restarts) ABCL-INTROSPECT Vastly improved support for Java object introspection (Used via as yet unreleased SLIME patches https://github.com/easye/slime.git) CL:DISASSEMBLE works "out of the box" with JAD (if installed on PATH), or Objectweb ABCL-AIO Package arbitrary run-time dependencies (both Java and Lisp) in 'abcl-aio.jar' for customized deployment scenarios ABCL-CONTRIB semantics described (UNIMPLEMENTED) Bootstrap the config mechanism across the network if a local abcl-contrib source tree cannot be located. JSS optimizations & features to support dynamic introspection ABCL-ASDF Robust Maven support -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."

2 4

How to call System.getProperty("user.home") from ABCL
by Mirko Vukovic 21 Jun '17

21 Jun '17

Hello, after a recent update of my company Windows 10 laptop, ABCL 1.4 is landing me in an incorrect home directory. Before I contact our support I would like to investigate the problem a bit more. This is how far I got: (user-homedir-pathname) returns #P"C:/WINDOWS/system32/config/systemprofile/" I wrote a little Java snippet to test "user.home" public class UserHome { public static void main(String[] args) { System.out.println(System.getProperty("user.home")); } } and it returns, correctly, "C:\Users\977315" I don't know how to call System.getProperty("user.home") from ABCL. I have multiple Java's on my laptop, and I need to doublecheck that my tests are self-consistent. But in the meantime, how do I call System.getProperty? Thanks, Mirko

4 8

ABCL User Question about following HTTP redirects for CL:OPEN on EXT:PATHNAME-URL references?
by Mark Evenson 04 Jun '17

04 Jun '17

Alan Ruttenberg from <http://abcl.org/trac/ticket/432>: So if you want to do something like use uiop/stream:copy-file which does something like open the source, open the dest, read/write, it will not do what you might expect. I don't see a way of controlling this behavior. Arguably the default ought to be to follow redirects and open the redirected-to file. I replied: ABCL-BUILD now uses uiop/steam:copy-file for the machinery which retreives XDG rooted Ant and Maven installations from well-known URIs c.f. <http://abcl.org/trac/browser/trunk/abcl/contrib/abcl-build/build/install.li…>, so the underlying ext:pathname-url implementation on java.net.HTTPUrlConnection seems to be working for cases in which the URI is already canonical in the form that would be idempotent for following across HTTP 3xx redirects. WORKAROUND: The current usage expected of the user is to introspect any reference to a ext:pathname-url via CL:TRUENAME. If there is an underlying redirect, CL:TRUENAME should somehow offer an API to the user to customize its behavior. I am currently against "jumping" across URI schema changes without a chance for user intervention. Smells like another restart to me. What would the current users of Armed Bear to do: automatically follow all HTTP retrieval redirects without regards to security concerns, or follow the current policy of doing "whatever ORCL thinks is right for java.net.HTTPUrlConnection"? -- "No, this is not a disentanglement, but a progressive /knotting-into/."

1 0

How to load the jna jar file before cffi?
by Mirko Vukovic 26 May '17

26 May '17

Hello, In order for CFFI to load, I need to load jna-4.2.2.jar. Right now, I have to do something like this: (let ((jar-pathname #P"c:/Users/977315/.m2/repository/net/java/dev/jna/jna/4.2.2/jna-4.2.2.jar")) (java:add-to-classpath (namestring jar-pathname))) To automate loading of ASDFs that require CFFI I tried to automate the process by adding a before method to 'load-op: (eval-when (:compile-toplevel :execute :load-toplevel) (defmethod operate :before ((operation (eql 'asdf/lisp-action:load-op)) (component (eql :cffi))) (let ((jar-pathname #P"c:/Users/977315/.m2/repository/net/java/dev/jna/jna/4.2.2/jna-4.2.2.jar")) (java:add-to-classpath (namestring jar-pathname))))) That did not work. I did read the ASDF manual, but could not figure out how to do it. I suspect someone has figured out the right way. What is it? Thanks, Mirko

3 8

Maven and ABCL
by Alan Ruttenberg 25 May '17

25 May '17

I'm using :mvn ASDF components and ran into a problem with having multiple versions of the same library. The issue boils down to the fact that ABCL currently processes dependencies for :mvn components one at a time, which doesn't take into account mutual dependencies. Attached is a function resolve-multiple-maven-dependencies, which takes a set of maven components and computes the dependencies. As an example, here is a comparison of treating the dependencies individually vs at once. (length (mapcan 'resolve-multiple-maven-dependencies '(("net.sourceforge.owlapi:owlapi-distribution:4.2.6") ("net.sourceforge.owlapi:org.semanticweb.hermit:1.3.8.413") ("org.semanticweb.elk/elk-reasoner/0.4.3") ("net.sourceforge.owlapi/pellet-cli-ignazio1977/2.4.0-ignazio1977") ("net.sourceforge.owlapi/owlexplanation/2.0.0")))) -> 210 (length (mapcan 'resolve-multiple-maven-dependencies '(("net.sourceforge.owlapi:owlapi-distribution:4.2.6" "net.sourceforge.owlapi:org.semanticweb.hermit:1.3.8.413" "org.semanticweb.elk/elk-reasoner/0.4.3" "net.sourceforge.owlapi/pellet-cli-ignazio1977/2.4.0-ignazio1977" "net.sourceforge.owlapi/owlexplanation/2.0.0")))) -> 90 In particular there are several versions of owlapi-distribution that are put on the classpath. Which one is actually used is not easily predictable. In my case even though I specified version 4.2.6 in my system definition, 4.1.3 was actually used. The attached code also has features not yet supported by the :mvn syntax that are really needed: The ability to override versions of a particular dependency that a downstream dependency specifies, and the ability to exclude certain artifacts altogether. Mark has suggested that the maven resolution could be moved to the ASDF planning stage, which sounds like a good idea. However there is still an issue regarding maven dependencies in different loaded ASDF systems. One idea is to remember dependencies across systems and then uses them as constraints on subsequent maven resolutions. Comments and ideas would be appreciated. Alan

3 11

sys:run-program errs on first invocation, works afterwards
by Mirko Vukovic 24 May '17

24 May '17

On Windows 10, ABCL 1.4.0 sys:run-program first issues an error. With abcl --no-init, the first call goes like this: (sys:run-program "where.exe" '("mvn.bat")) Error message: Class not found: java.lang.UNIXProcess [Condition of type ERROR] ... 48: (JCLASS "java.lang.UNIXProcess") 49: (SYSTEM::GET-FASL-FUNCTION #<org.armedbear.lisp.FaslClassLoader org.armedbear.lisp.FaslClassLoad.... {445C74}> 48) 50: (SYSTEM:INIT-FASL :VERSION 42) 51: (SYSTEM::%EVAL (SYSTEM:RUN-PROGRAM "where.exe" '("mvn.bat"))) Repeating the command the second time, and parsing the output (as done in abcl-asdf:find-mvn) gives the expected result. Mirko

1 0

Finding abcl-contrib packages inside a JAR: approach and suggestions
by Frederico Munoz 30 Apr '17

30 Apr '17

Hello, I'm almost done with my small experiment: * I'm loading lisp code via a Java file using Load.loadSystemFile in an init method * I'm adding the file file to *lisp-home* via gradle * I'm using gradle tasks to create a single JAR with abcl and abcl-contrib added (not as JAR files) Note that I need to have only one jar file and with specific requirements around the main method; the above allows me to have it working fine, a single JAR which is essentially standalone. My only remaining doubt (apart from other possible solutions which could also work and be more elegant, I'm open to suggestions of course) is around loading abcl-contrib.jar or more specifically the included packages (JSS and JFLI specifically). I've spent some hours tracking the loading mechanism and learned a bit about the process but I'm still missing some pieces. My current solution (which works) is: (require :abcl-contrib) (pushnew (make-pathname :device (pathname-device *lisp-home*) :directory '(:absolute "jss")) asdf:*central-registry*) (require :jss) This adds #P"jar:file:/foo/myapp.jar!/jss" to ASDF, but I would like something more direct. With my setup (system::find-contrib) returns NIL; I've tried to add the abcl-contrib.jar to myapp.jar (which is in the CLASSPATH of course) but the code on abcl-contrib.lisp (and specifically find-contrib) doesn't seem to seach inside a jar for another one. I also tried to use something like (system::add-contrib (make-pathname :device (pathname-device *lisp-home*) :directory '(:absolute "abcl-contrib.jar"))) to see if it would pick up the jar but no luck. I think there is something obvious I'm missing, the pieces are all there (the jar handling code works fine, etc) but I can't seem to find the right way to put them together. Best regards, -- fsmunoz(a)sdf.org SDF Public Access UNIX System - http://sdf.org

2 2

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-devel