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 <
[email protected]> 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!
>
>
_______________________________________________
Gnustep-dev mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Reply via email to