Comments on: Using native Objective-C methods for C Callbacks http://www.eisbox.net/2008/10/11/375-using-native-objective-c-methods-for-c-callbacks/ ... projects, thoughts, etc. Mon, 06 Sep 2010 06:08:50 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Rastikan http://www.eisbox.net/2008/10/11/375-using-native-objective-c-methods-for-c-callbacks/comment-page-1/#comment-13557 Rastikan Fri, 03 Jul 2009 00:45:47 +0000 http://www.eisbox.net/?p=375#comment-13557 Hi there, Just stumbled on your blog post. I was wondering about the opposite problem... I have some C code that I want to keep plain C because it is going to be embedded code. This is just some state machine code I am developing from within a Bluetooth ObjC sample code. Basically I would need to callback into ObjC object merely for using the OSX RFCOMM Bluetooth API. Just so the C code isn't clobbered with OSX function calls, I'd use a wrapping C function (send_data) that really callback the ObjC and then into RFCOMM stuff. In the embedded version, the same send_data would rather talk to some radio instead of RFCOMM stack. Hi there,

Just stumbled on your blog post. I was wondering about the opposite problem…

I have some C code that I want to keep plain C because it is going to be embedded code. This is just some state machine code I am developing from within a Bluetooth ObjC sample code.

Basically I would need to callback into ObjC object merely for using the OSX RFCOMM Bluetooth API. Just so the C code isn’t clobbered with OSX function calls, I’d use a wrapping C function (send_data) that really callback the ObjC and then into RFCOMM stuff. In the embedded version, the same send_data would rather talk to some radio instead of RFCOMM stack.

]]>