What the hell is this???

[Cedric Greevey]

I'm not sure if this is a bug in clooj or in Clojure itself:


Evaluating file...CompilerException java.lang.ClassFormatError: Unknown constant tag 117 in class file [redacted]/core$eval215, compiling:(NO_SOURCE_PATH:156:1034)

What *is* certain is that nothing I type into the source code should be able to cause ClassFormatError. So the bug isn't mine.

Now, someone tell me how to fix it.

[Devin Walters]

Context would help.

--
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clo...@googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
clojure+u...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojure+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Cedric Greevey]

In case you hadn't noticed, there *is* no context. No source file and the line number and column refer to, apparently, the REPL buffer and not the source file. The $eval215 clearly indicates that it's the compiled bytecode of the REPL evaluation itself that it objected to, not the compiled bytecode of any of the individual functions or other defs in the source file. And it's the *compiled bytecode* it didn't like, *not* the source code. The source code parsed without syntax errors, unresolved symbols, or anything else, and was successfully compiled to bytecode that, when executed, *should* have performed a series of defs into a namespace. But the compiler emitted incorrect bytecode after having apparently successfully parsed the input.

That's a compiler bug, pretty much by definition. Even if there is some subtle error in the input, the compiler should report it, *not* silently generate incorrect bytecode while apparently succeeding, then complain when attempting to invoke said bytecode makes the JVM vomit.

--
You received this message because you are subscribed to the Google Groups "clooj" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clooj+un...@googlegroups.com.