I've just updated my Core Foundation wrapper classes. There are two
real changes. First, I added a debug mode to the CFBundle class, so
that you can use the routines for loading resources in an app running
in the debugger.
Second, I changed the CFObject constructor to default to retaining
objects. I ignored some good advice from Brady Duga on this point
until now, but finally decided I was allowing internal implementation
details to dictate the interface, which is a bad thing to do.
So, from now on, if you do:
someStr = new CFString(stringObjectRef)
the CFString referenced by stringObjectRef will be retained. If you
do not want the object to be retained, you would do:
someStr = new CFString(stringObjectRef, false)
--
-Thomas
Personal web page: <http://homepage.mac.com/thomasareed/>
My shareware: <http://www.bitjuggler.com/>
Free REALbasic code: <http://www.bitjuggler.com/extra/>
There are 10 kinds of people in the world -- those who understand binary
numbers and those who don't.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://support.realsoftware.com/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|