>> Thanks, changing several methods to use the 'new..." naming standard did >> the trick. Using create as suggested by Wade didn't fix the problem, which >> explains why another method (createBitmapContext) was showing similar >> behavior. > > Create only works with functions (CF convention). new only works with methods > (Cocoa convention).
My apologies, I was extrapolating from 'copy', which is supported in both. Tangentially, I find it odd that 'new' is recognised as it puts me in mind of the old 'new' class method, which has been deprecated and frowned upon for as long as I can remember. Wade _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
