[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSString's -isEqual: problems

From: Stefan Bidi
Subject: Re: NSString's -isEqual: problems
Date: Sun, 10 Jul 2011 11:12:15 -0500

Actually, my bad.  The -rangeOfComposedCharactersAtIndex: method in NSString is, in fact, implemented.  It's -rangeOfComposedCharacterSequencesForRange: that's not.  I apparently just made some noise for absolutely no reason.

On Sun, Jul 10, 2011 at 11:02 AM, Richard Frith-Macdonald <address@hidden> wrote:

On 10 Jul 2011, at 16:54, Stefan Bidi wrote:

> Sorry to be replying to my own e-mail, but I figured it out...
> GSEQ_STRCOMP() calls -rangeOfComposedCharactersAtIndex: and CFString was just returning {0, 0} for that call.  I still can't really follow what this function does, but that seems like a weird method to call since NSString just return {0, 0}, as well

That's a bug!

reply via email to

[Prev in Thread] Current Thread [Next in Thread]