FROM : John Stiles
DATE : Tue Sep 11 04:46:50 2007
Hmm. Well, that's a reasonable obstacle. But still, it seems as if
Apple could have implemented it the "slow" way for now (where it
converts each string to a buffer before regex'ing it), and then once
this bug gets implemented, convert the OS to use the "fast" way. That
way the API could internally be improved over time while the
interface stays the same.
Or is there another reason why it couldn't be done this way...?
Also, FWIW, there are plenty of internal Apple projects which already
mix regular expressions and NSStrings—Xcode comes to mind—so again,
it doesn't seem like a total blocker. Just maybe a short-term perf
issue.
On Sep 10, 2007, at 7:09 PM, Deborah Goldsmith wrote:
> We definitely want this to happen, but it's a lot of work. This is
> the current roadblock:
>
> http://bugs.icu-project.org/trac/ticket/4521
>
> Please note the number of weeks estimated for implementation.
>
> Sorry for the long wait...
>
> Deborah Goldsmith
> Internationalization, Unicode Liaison
> Apple Inc.
> <email_removed>
>
> On Sep 6, 2007, at 7:32 AM, Mark Munz wrote:
>
>> Come on. 64b support is different than flashy animations and you
>> know it.
>>
>> Apple has a habit of making every developer repeat the same basic
>> work
>> that should be part of the system. Even with ICU included, you still
>> have to jump through a number of hoops to use it with NSStrings. They
>> know it (based on a conversation I had in 2006 at WWDC).
>>
>> Rather than fix the problem once, they basically force each developer
>> to "fix" the problem. And this is a pattern that is decades old.
>>
>> On 9/6/07, Shawn Erickson <<email_removed>> wrote:
>>>
>>> On Sep 6, 2007, at 7:05 AM, Mark Munz wrote:
>>>
>>>> and Apple
>>>> apparently doesn't feel addressing this issue is more important
>>>> than
>>>> animating the views as they slide around the screen.
>>>
>>> Yeah also why did they waste time adding 64b support when the could
>>> have been adding something a developer could have picked up
>>> themselves if they really needed it.
>>>
>>> -Shawn
>>>
>>
>>
>> --
>> Mark Munz
>> unmarked software
>> http://www.unmarked.com/
>> _______________________________________________
>>
>> Cocoa-dev mailing list (<email_removed>)
>>
>> 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_removed>
>>
>> This email sent to <email_removed>
>
> _______________________________________________
>
> Cocoa-dev mailing list (<email_removed>)
>
> 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/jstiles%
> 40blizzard.com
>
> This email sent to <email_removed>
DATE : Tue Sep 11 04:46:50 2007
Hmm. Well, that's a reasonable obstacle. But still, it seems as if
Apple could have implemented it the "slow" way for now (where it
converts each string to a buffer before regex'ing it), and then once
this bug gets implemented, convert the OS to use the "fast" way. That
way the API could internally be improved over time while the
interface stays the same.
Or is there another reason why it couldn't be done this way...?
Also, FWIW, there are plenty of internal Apple projects which already
mix regular expressions and NSStrings—Xcode comes to mind—so again,
it doesn't seem like a total blocker. Just maybe a short-term perf
issue.
On Sep 10, 2007, at 7:09 PM, Deborah Goldsmith wrote:
> We definitely want this to happen, but it's a lot of work. This is
> the current roadblock:
>
> http://bugs.icu-project.org/trac/ticket/4521
>
> Please note the number of weeks estimated for implementation.
>
> Sorry for the long wait...
>
> Deborah Goldsmith
> Internationalization, Unicode Liaison
> Apple Inc.
> <email_removed>
>
> On Sep 6, 2007, at 7:32 AM, Mark Munz wrote:
>
>> Come on. 64b support is different than flashy animations and you
>> know it.
>>
>> Apple has a habit of making every developer repeat the same basic
>> work
>> that should be part of the system. Even with ICU included, you still
>> have to jump through a number of hoops to use it with NSStrings. They
>> know it (based on a conversation I had in 2006 at WWDC).
>>
>> Rather than fix the problem once, they basically force each developer
>> to "fix" the problem. And this is a pattern that is decades old.
>>
>> On 9/6/07, Shawn Erickson <<email_removed>> wrote:
>>>
>>> On Sep 6, 2007, at 7:05 AM, Mark Munz wrote:
>>>
>>>> and Apple
>>>> apparently doesn't feel addressing this issue is more important
>>>> than
>>>> animating the views as they slide around the screen.
>>>
>>> Yeah also why did they waste time adding 64b support when the could
>>> have been adding something a developer could have picked up
>>> themselves if they really needed it.
>>>
>>> -Shawn
>>>
>>
>>
>> --
>> Mark Munz
>> unmarked software
>> http://www.unmarked.com/
>> _______________________________________________
>>
>> Cocoa-dev mailing list (<email_removed>)
>>
>> 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_removed>
>>
>> This email sent to <email_removed>
>
> _______________________________________________
>
> Cocoa-dev mailing list (<email_removed>)
>
> 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/jstiles%
> 40blizzard.com
>
> This email sent to <email_removed>






Cocoa mail archive

