Re: deprecated carbon calls?
Re: deprecated carbon calls?
- Subject: Re: deprecated carbon calls?
- From: "Eric Wagner" <email@hidden>
- Date: Tue, 27 Mar 2007 18:00:12 -1000
Try placing #define BLUETOOTH_VERSION_USE_CURRENT on a line before you
include the Framework headers. Take a look at
http://bluecove.googlecode.com/svn/branches/osxPort/. Its currently a
messy Java wrapper for OS X Bluetooth.
The next problem you'll run into is the lack of a garbage collector if
you are using C code, the ThreadCleanups.m file fixes this. The linker
has no problem linking C, C++ and cocoa. You'll run into more problems
in that a lot of the libraries now assume that the running thread has
been initialized in certain respects. Something that is done
automatically for cocoa threads.
On 3/27/07, Daniel Birns <email@hidden> wrote:
I found this wonderfully useful posting in the maillist from Bubba Giles,
appended, which works and which we're basing our carbon bluetooth app on.
However, the compiler says that virtually all the calls are deprecated. I
can't find any information on this.
Also, the note appended seems to indicate the cocoa is more reliable.
One possibility is that I write the bluetooth code in cocoa for
reliability. if so, how should I mix the two??? Can you have objects in
cocoa and some objects in carbon? Should I have 2 binaries that communicate
via sockets??? (Geez what a lot of work that would be).
I'd really prefer to stay in carbon, but I'm concerned about the deprecated
messages.
Thanks.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden