On Jul 27, 2013, at 2:05 PM, Zac Bowling <z...@zacbowling.com> wrote:
> The first one is a NSConstantString string. It's not like a malloc'd > NSString. It's effectively a singleton. It doesn't mater how it's bridged > because it can't be released. The second is a new NSURL that is allocated on > the heap. It needs to be released so it needs to be bridged correctly to > handle things properly. CFStringGetIntValue() is passed an NSString * variable (casted to a CFStringRef). The fact that a constant string was assigned to it earlier is neither here nor there. As far as that function knows, that variable could contain an NSConstantString, an NSMutableString, an NSCFString, an NSPathStore2, or any other subclass of NSString. For the record, I tried his example, assigning an NSMutableString to the "answer" variable and got the same result. On Jul 27, 2013, at 2:16 PM, Matt Neuburg <m...@tidbits.com> wrote: > Argh. Okay, I'll ask this on devforums when it comes back up, in case it > depends on, uh, the thing I'm using that I can't talk about. m. I seem to be able to reproduce it in 4.6.3, so it's not solely dependent on The IDE Who Must Not Be Named. Charles _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
