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>
26 lines
630 B
Plaintext
26 lines
630 B
Plaintext
// Objective-C API for talking to interfaces Go package.
|
|
// gobind -lang=objc interfaces
|
|
//
|
|
// File is generated by gobind. Do not edit.
|
|
|
|
#ifndef __interfaces_H__
|
|
#define __interfaces_H__
|
|
|
|
#include <stdint.h>
|
|
#include <objc/objc.h>
|
|
int32_t cproxyinterfaces_Error_Err(int32_t refnum);
|
|
|
|
int32_t cproxyinterfaces_I_Rand(int32_t refnum);
|
|
|
|
int32_t cproxyinterfaces_I3_F(int32_t refnum);
|
|
|
|
void cproxyinterfaces_LargerI_AnotherFunc(int32_t refnum);
|
|
|
|
int32_t cproxyinterfaces_LargerI_Rand(int32_t refnum);
|
|
|
|
int32_t cproxyinterfaces_SameI_Rand(int32_t refnum);
|
|
|
|
void cproxyinterfaces_WithParam_HasParam(int32_t refnum, char p0);
|
|
|
|
#endif
|