As per my understanding Carbon framework will be deprecated or completely removed in future versions of OSX. Well that's the only reason I wish to remove the carbon framework from my application now.
On Fri, Nov 21, 2008 at 3:21 PM, Jean-Daniel Dupas <[EMAIL PROTECTED]>wrote: > > Le 21 nov. 08 à 10:42, spsaxena a écrit : > > > Hi all, >> I am working on making my application carbon free. I could not find any >> replacement for the API "GetApplicationTextEncoding" probably because this >> API has not been marked as deprecated yet. Because of this API I need to >> link with the carbon framework which I don't want. Can you please suggest >> any non-carbon API as a replacement for this API. >> >> Thanks, >> S! >> > > Is there any valid reason you do not want to link on Carbon at all ? > Some functionality are only available in Carbon. > > I don't see what is bad in using a function that is not deprecated and > marked as available on 64bits. > >
_______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
