java: Unpickler should handle `Opcodes.OBJ`

Came across this issue when unpickling “callable class” instances.

By observing Python2.7 and Python 3.4 pickle.py files, I’ve managed to provide a temporary handler like this:

Unpickler unpickler = new Unpickler(){

	@Override
	protected Object dispatch(short key) throws IOException {
		switch(key){
			case Opcodes.OBJ:
				return load_obj();
			default:
				return super.dispatch(key);
		}
	}

	private Object load_obj(){
		List<Object> args = super.stack.pop_all_since_marker();
		IObjectConstructor constructor = (IObjectConstructor)args.get(0);
		args = args.subList(1, args.size());
		Object object = constructor.construct(args.toArray());
		super.stack.add(object);

		return noReturnValue();
	}
};

[vruusmann]

@irmen I can confirm that Pyrolite 4.17-SNAPSHOT addresses my current needs completely - there is no need for subclassing Unpickler anymore, and my test suite (involves unpickling ~100 rather complex data structures) passes cleanly.

Never had any problems with Pyrolite. Awesome work!

[irmen]

new version 4.17 has been pushed