| commit | a9aa4349d280fe6e0234bf478c19b594a6900bd3 | [log] [tgz] |
|---|---|---|
| author | Alex Fandrianto <alexfandrianto@google.com> | Tue Jun 28 20:19:34 2016 -0700 |
| committer | Alex Fandrianto <alexfandrianto@google.com> | Fri Jul 01 22:57:53 2016 +0000 |
| tree | 2ba43148d53d8bf2328cffad8c25a18ab9573b52 | |
| parent | 156d4aef628d5aec0e23e5ef03c2c4a5aece9225 [diff] |
x/ref: Avoid JNI DETECTED ERROR IN APPLICATION error I noticed that if I try to return a non-primitive object during an exception (such as during SyncgroupJoin) that the jni would crash. This error seems to imply that we have to wait for Java to handle the exception OR clear the exception OR just return early (with null). I opted for returning early. The JNI functions that return errors and primitives remain as-is since the latter can't be nil'd. Change-Id: If7d88ee72cead5a6f0c0d38061a2f309570089d3
This repository contains a reference implementation of the Vanadium APIs.
Unlike the APIs in https://github.com/vanadium/go.v23, which promises to provide backward compatibility this repository makes no such promises.