2015-08-25 16:39:49 -04:00
|
|
|
// Objective-C API for talking to issue12328 Go package.
|
|
|
|
|
// gobind -lang=objc issue12328
|
|
|
|
|
//
|
|
|
|
|
// File is generated by gobind. Do not edit.
|
|
|
|
|
|
|
|
|
|
#ifndef __GoIssue12328_H__
|
|
|
|
|
#define __GoIssue12328_H__
|
|
|
|
|
|
|
|
|
|
#include <Foundation/Foundation.h>
|
mobile/bind: use objects to pass errors across the language barrier
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>
2016-06-14 11:58:31 +02:00
|
|
|
#include "GoUniverse.h"
|
2015-08-25 16:39:49 -04:00
|
|
|
|
|
|
|
|
@class GoIssue12328T;
|
|
|
|
|
|
|
|
|
|
@interface GoIssue12328T : NSObject {
|
|
|
|
|
}
|
2015-10-12 15:50:24 -04:00
|
|
|
@property(strong, readonly) id _ref;
|
2015-08-25 16:39:49 -04:00
|
|
|
|
|
|
|
|
- (id)initWithRef:(id)ref;
|
2016-09-14 18:04:50 +02:00
|
|
|
- (NSError*)err;
|
|
|
|
|
- (void)setErr:(NSError*)v;
|
2015-08-25 16:39:49 -04:00
|
|
|
@end
|
|
|
|
|
|
|
|
|
|
#endif
|
