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>
32 lines
724 B
Plaintext
32 lines
724 B
Plaintext
// Objective-C API for talking to issue12403 Go package.
|
|
// gobind -lang=objc issue12403
|
|
//
|
|
// File is generated by gobind. Do not edit.
|
|
|
|
#ifndef __GoIssue12403_H__
|
|
#define __GoIssue12403_H__
|
|
|
|
#include <Foundation/Foundation.h>
|
|
#include "GoUniverse.h"
|
|
|
|
@protocol GoIssue12403Parsable;
|
|
@class GoIssue12403Parsable;
|
|
|
|
@protocol GoIssue12403Parsable
|
|
- (NSString*)fromJSON:(NSString*)jstr;
|
|
- (BOOL)toJSON:(NSString**)ret0_ error:(NSError**)error;
|
|
@end
|
|
|
|
@class GoIssue12403Parsable;
|
|
|
|
@interface GoIssue12403Parsable : NSObject <GoIssue12403Parsable> {
|
|
}
|
|
@property(strong, readonly) id _ref;
|
|
|
|
- (id)initWithRef:(id)ref;
|
|
- (NSString*)fromJSON:(NSString*)jstr;
|
|
- (BOOL)toJSON:(NSString**)ret0_ error:(NSError**)error;
|
|
@end
|
|
|
|
#endif
|