type mismatch mystery solved

Reid,

I finally figured out why my types were mismatching in my hand-decoded bytecode example when it worked fine in my actual code. It turns out that I was not leaving out the extension bits when I was hand decoding the VBRs. D'oh! Everything matches up now.

Also figured out why the bcanalyzer is spitting out all those pointers to opaque. These types are forward references and they are getting printed out before they're resolved. Easy to fix.

-- Robert.

Hi Robert,

Reid,

I finally figured out why my types were mismatching in my hand-decoded
bytecode example when it worked fine in my actual code.

Great!

It turns out
that I was not leaving out the extension bits when I was hand decoding
the VBRs. D'oh!

Heh, its always the little things :slight_smile:

Everything matches up now.

Wonderful.

Also figured out why the bcanalyzer is spitting out all those pointers
to opaque. These types are forward references and they are getting
printed out before they're resolved. Easy to fix.

Right. That makes sense. The reader uses opaque to handle forward
references until they are resolved.

Reid.