1) There are certain basics like regex support that people are upset
at Apple for not implementing because it seems like such an important
part of the concept of strings.
Agreed, and I made this argument many times while there. Part of the
problem is the impedance mismatch issue — Apple would want to use ICU
because of its good Unicode support, but the way the ICU APIs are
written generally requires copying the string to a temporary buffer
(especially if you consider thread-safety.) There has been talk of
extending ICU regexps to support plug-in string storage, which would
be more efficient, and as far as I can tell, the whole regexps-for-
Cocoa feature gets hung up on waiting for that, year after year.
Filing bugs on it is going to annoy people on the Cocoa team at Apple
because they'll have to flag them all as dups and send them back; but
it's the only lever that's been given to 3rd party developers to
influence this, so I can't fault anyone for yanking it.
4) Linking against a third-party framework requires distributing the
framework inside the app bundle. Look at the proliferation of
Sparkle.framework to see why this is a Bad Thing(TM).
Not if it's in the OS, which most all of the regexp libraries are. (I
know, you mean the Obj-C adapter framework, but in the case of
RegexpKit-Lite that's just one class / source file, which I don't see
as a problem. Just statically link it into your app.)
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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/email@hidden
This email sent to email@hidden
