I do not think this is necessary. With Objective-C ++, you don't need a bridge at all. Given a specific C ++ class
class Foo {
public:
void someMethod(void);
}
you can use this class anywhere in Objective-C ++ code. For example, as part of a method:
- (void)myObjCMethod {
Foo myFoo;
myFoo.someMethod();
}
You can have instance variables that point to C ++ classes, so you can define an Objective-C class, for example
@interface Bar : NSObject {
Foo *foo;
}
@property (assign) Foo * foo;
@end
@implementation
@synthesize foo;
- (void)dalloc {
delete foo;
[super dealloc];
}
- (id)init {
if(self = [super init]) {
foo = new Foo();
}
return self;
}
- (void)aMethod {
self.foo->barMethod();
}
I don't think you can create an Objective-C template, but instances of C ++ templates in Objective-C ++ are fair game. Just as Objective-C is a strict superset of C, Objective-C ++ is a superset of C ++ that adds Objective-C classes and message passing.
"" ++, , , , Objective-C.