Hi, Is there problem with the contrib/swank-kawa.scm? COMPILE-FILE in Kawa 1.9.1 REPL complains that gnu.text.SyntaxException: /home/vy/elisp/slime/contrib/swank-kawa.scm:2062:1: '(* 1 st$unit)' is not a valid identifier at kawa.lib.system.compileFile(system.scm:94) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at gnu.expr.PrimProcedure.apply(PrimProcedure.java:251) at gnu.mapping.CallContext.runUntilDone(CallContext.java:251) at gnu.expr.ModuleExp.evalModule(ModuleExp.java:296) at kawa.Shell.run(Shell.java:230) at kawa.Shell.run(Shell.java:172) at kawa.Shell.run(Shell.java:159) at kawa.repl.main(repl.java:844) Regards.
* Volkan YAZICI [2008-10-11 15:54+0200] writes:
Hi,
Is there problem with the contrib/swank-kawa.scm? COMPILE-FILE in Kawa 1.9.1 REPL complains that
gnu.text.SyntaxException: /home/vy/elisp/slime/contrib/swank-kawa.scm:2062:1: '(* 1 st$unit)' is not a valid identifier
I don't think that swank-kawa.scm runs in 1.9.1. You need the SVN version of Kawa. In 1.9.1 "1st" was parsed differently. You also need the newest CVS version of SLIME, because there were some changes/bugs which are only fixed in the version of today. Helmut.
On Sat, 11 Oct 2008, Helmut Eller <heller@common-lisp.net> writes:
I don't think that swank-kawa.scm runs in 1.9.1. You need the SVN version of Kawa. In 1.9.1 "1st" was parsed differently.
When I saw 2007 date at the beginning of the swank-kawa.scm, I thought that the latest SVN tip dependency should have been deprecated. But it seems to be not. This can be a trivial problem, but I still couldn't manage to compile swank-kawa.scm using kawa: rlwrap java \ -classpath /home/vy/usr/share/java/kawa.jar:/usr/local/java/jdk/1.6.0_06/lib/sa-jdi.jar \ -Xdebug \ kawa.repl #|kawa:1|# (compile-file "/home/vy/elisp/slime/contrib/swank-kawa.scm" "swank-kawa") java.lang.RuntimeException: no such class: com.sun.jdi.Location at gnu.bytecode.ObjectType.getReflectClass(ObjectType.java:125) at gnu.bytecode.ClassType.addFields(ClassType.java:581) at gnu.bytecode.ClassType.getFields(ClassType.java:485) at gnu.bytecode.ClassType.getDeclaredField(ClassType.java:499) at gnu.bytecode.ClassType.getField(ClassType.java:518) at gnu.kawa.reflect.SlotGet.lookupMember(SlotGet.java:209) at kawa.lang.Translator.rewrite(Translator.java:641) ... Suprisingly google returned nothing for quoted "no such class: com.sun.jdi.Location". What might I be missing in the above "Sun JVM with debugger support"?
You also need the newest CVS version of SLIME, because there were some changes/bugs which are only fixed in the version of today.
Yep, did a "cvs up -C -d -P -r HEAD". Regards.
* Volkan YAZICI [2008-10-12 10:12+0200] writes:
On Sat, 11 Oct 2008, Helmut Eller <heller@common-lisp.net> writes:
I don't think that swank-kawa.scm runs in 1.9.1. You need the SVN version of Kawa. In 1.9.1 "1st" was parsed differently.
When I saw 2007 date at the beginning of the swank-kawa.scm, I thought that the latest SVN tip dependency should have been deprecated. But it seems to be not.
This can be a trivial problem, but I still couldn't manage to compile swank-kawa.scm using kawa:
rlwrap java \ -classpath /home/vy/usr/share/java/kawa.jar:/usr/local/java/jdk/1.6.0_06/lib/sa-jdi.jar \ -Xdebug \ kawa.repl #|kawa:1|# (compile-file "/home/vy/elisp/slime/contrib/swank-kawa.scm" "swank-kawa") java.lang.RuntimeException: no such class: com.sun.jdi.Location at gnu.bytecode.ObjectType.getReflectClass(ObjectType.java:125) at gnu.bytecode.ClassType.addFields(ClassType.java:581) at gnu.bytecode.ClassType.getFields(ClassType.java:485) at gnu.bytecode.ClassType.getDeclaredField(ClassType.java:499) at gnu.bytecode.ClassType.getField(ClassType.java:518) at gnu.kawa.reflect.SlotGet.lookupMember(SlotGet.java:209) at kawa.lang.Translator.rewrite(Translator.java:641) ...
Suprisingly google returned nothing for quoted "no such class: com.sun.jdi.Location". What might I be missing in the above "Sun JVM with debugger support"?
com.sun.jdi.Location is probably in JAVAHOME/lib/tools.jar not in sa-jdi.jar. Helmut.
Volkan YAZICI <yazicivo@ttmail.com> writes:
Suprisingly google returned nothing for quoted "no such class: com.sun.jdi.Location". What might I be missing in the above "Sun JVM with debugger support"?
I thought JDI was in the Java Standard Edition. What version are you running? Cheers, Chris Dean
participants (3)
-
Chris Dean -
Helmut Eller -
Volkan YAZICI