> Yes, 1.3 supports only long and double primitives as local variables.
> But the bug doesn't seem to be new. I get the same error if I try to
> assign an int into a long deftype field in 1.2.
>
>
So there is a bug in the way bad primitive assignement are reported or handled.
Has it been reported
On Nov 19, 6:34 pm, "nicolas.o...@gmail.com"
wrote:
> I found a minimal case:
>
> (defprotocol A (f [x]))
>
> (deftype T [ ^{:unsynchronized-mutable true} ^int a] A
> (f [x] (loop [c 0]
> (set! a c
>
> (class: user/T, method: f signature: ()Ljava/lang/
I found a minimal case:
(defprotocol A (f [x]))
(deftype T [ ^{:unsynchronized-mutable true} ^int a] A
(f [x] (loop [c 0]
(set! a c
(class: user/T, method: f signature: ()Ljava/lang/Object;) Expecting
to find integer on stack
The problem disappear
Thank you very much.
I will have a look at that tomorrow or try to extract a minimal code
for the problem.
Just to make sure: has there been any syntax change to definterface?
(To make it closer to defprotocol for example)
Best,
Nicolas.
On Thu, Nov 18, 2010 at 2:06 PM, Stuart Sierra
wrote:
>
On Nov 17, 12:31 pm, "nicolas.o...@gmail.com"
wrote:
> I am trying top port some code from 1.2 to 1.3 and I end up with this error:
>
> Unknown location:
> error: java.lang.VerifyError: (class:
Wow, that looks like a binary compatibility error. Make sure you're
starting with a clean directory
