a3e0621280
Gobind uses strings for passing errors across the language barrier. However, since Gobind doesn't have a concept of a nil string, it can't separate an empty native string from a nil string. In turn, that means that empty errors, exceptions or NSError * with an empty description are treated as no error. With ObjC, empty errors are replaced with a default string to workaround the issue, while with Java empty errors are silently ignored. Fix this by replacing strings with actual error objects, wrapping the Go error, Java Throwable or ObjC NSError *, and letting the existing bind machinery take care of passing the references across. It's a large change for a small corner case, but I believe objects are a better fit for exception that strings. Error objects also naturally leads to future additions, for example accessing the exception class name or chained exception. Change-Id: Ie03b47cafcb231ad1e12a80195693fa7459c6265 Reviewed-on: https://go-review.googlesource.com/24100 Reviewed-by: David Crawshaw <crawshaw@golang.org>
23 lines
619 B
Plaintext
23 lines
619 B
Plaintext
// JNI function headers for the Go <=> Java bridge.
|
|
// gobind -lang=java issue12403
|
|
//
|
|
// File is generated by gobind. Do not edit.
|
|
|
|
#ifndef __Issue12403_H__
|
|
#define __Issue12403_H__
|
|
|
|
#include <jni.h>
|
|
|
|
extern jclass proxy_class_issue12403_Parsable;
|
|
extern jmethodID proxy_class_issue12403_Parsable_cons;
|
|
|
|
nstring cproxyissue12403_Parsable_FromJSON(int32_t refnum, nstring jstr);
|
|
|
|
typedef struct cproxyissue12403_Parsable_ToJSON_return {
|
|
nstring r0;
|
|
int32_t r1;
|
|
} cproxyissue12403_Parsable_ToJSON_return;
|
|
struct cproxyissue12403_Parsable_ToJSON_return cproxyissue12403_Parsable_ToJSON(int32_t refnum);
|
|
|
|
#endif
|