CPString compare: implementation

I'm not sure to understand why you pass CPLitteralSearch as an option for compare:

From Cocoa documentation:

NSString compare: Returns the result of invoking compare:options:range: with no options and the receiver’s full extent as the range.

Because if you read the documentation a bit more you will see:

Search and comparison are currently performed as if the NSLiteralSearch option were specified.

Which is how I've implemented it.

Sorry, I see what you mean. I should specify it as nil and let it fall through to the default behavior. I'll tweak and resubmit.

Attaching second patch for this... now uses nil as the second argument

ok coolTakayama , so we agree. Now it could be interesting to work on these unimplemented options for compare:options: I think NSLitteralSearch does not apply to javascript but I need an opinion of a javascript insider. NSNumericSearch requires some scanning. I have a NSDiacriticInsensitive (10.5 innovation) partial implementation for roman alphabet that I could submit if needed.

Your second patch doesn't work, because it require the first. You can pass specific revisions to diff to git, so in the future, it would be best if you make sure to generate the full patch against whatever Cappuccino's HEAD is.

For this one, I'll manually make the necessary changes.