FROM : cocoa-dev-admins >
DATE : Tue Sep 11 20:21:09 2007
Although this subject may be very interesting to some readers, with well
over 4000 subscribers to cocoa-dev, it's important we keep the subjects on
topic.
I encourage you to file an enhancement request through
bugreporter.apple.com, or please take the discussion off-line.
Thanks,
Cocoa-Dev Admins
> On 9/11/07, Alastair Houghton <<email_removed>> wrote:
>
>> That's all true, but why release an implementation at all if there
>> are third-party alternatives that are just as simple to use and if
>> your implementation has no performance or other advantages?
>
> There are some 3rd party options, but they come with their own set of
> issues. Just because I want to use regexps does not mean I want to be
> forced to become an expert in the underlying engine code.
>
>> Particularly if there's a risk (and I think there is) that the API
>> you come up with might have to change because of major architectural
>> work going on on the underlying ICU code.
>
> Are you just assuming this might be the case or are there actual major
> architectural changes taking place in the underlying ICU code with the
> next release of the library?
>
>> In such a situation, I'd rather they didn't rush. Apparently Mark
>> Munz feels differently, but I don't think we're going to achieve
>> anything useful by debating the matter further.
>
> Rushing? Mind you, I'm pretty sure it's not going to be in Leopard --
> so we're already looking at Leopard + 1, which means at least 2010,
> maybe 2011 before support *might* show up. The issue is *at least* 2
> years old. And we're assuming it doesn't get pushed back yet again (as
> it has for the last 2 years).
>
>> Right now there isn't an NSRegularExpression, and it looks like
>> there's more work necessary before we get one. So we can use one of
>> various third-party frameworks, or directly use one of various third-
>> party libraries.
>
> Yes, the same argument can be made for features like Source lists and
> Media Browsing. Just because there is a work around doesn't mean there
> shouldn't be a solution included in the current Cocoa frameworks.
>
> While there are 3rd party options, they aren't all consistent in their
> syntax and options. So any regexp exposed to the end user is subject
> to inconsistent behavior from their point of view. Having a common
> library supported by the OS helps eliminate that issue.
DATE : Tue Sep 11 20:21:09 2007
Although this subject may be very interesting to some readers, with well
over 4000 subscribers to cocoa-dev, it's important we keep the subjects on
topic.
I encourage you to file an enhancement request through
bugreporter.apple.com, or please take the discussion off-line.
Thanks,
Cocoa-Dev Admins
> On 9/11/07, Alastair Houghton <<email_removed>> wrote:
>
>> That's all true, but why release an implementation at all if there
>> are third-party alternatives that are just as simple to use and if
>> your implementation has no performance or other advantages?
>
> There are some 3rd party options, but they come with their own set of
> issues. Just because I want to use regexps does not mean I want to be
> forced to become an expert in the underlying engine code.
>
>> Particularly if there's a risk (and I think there is) that the API
>> you come up with might have to change because of major architectural
>> work going on on the underlying ICU code.
>
> Are you just assuming this might be the case or are there actual major
> architectural changes taking place in the underlying ICU code with the
> next release of the library?
>
>> In such a situation, I'd rather they didn't rush. Apparently Mark
>> Munz feels differently, but I don't think we're going to achieve
>> anything useful by debating the matter further.
>
> Rushing? Mind you, I'm pretty sure it's not going to be in Leopard --
> so we're already looking at Leopard + 1, which means at least 2010,
> maybe 2011 before support *might* show up. The issue is *at least* 2
> years old. And we're assuming it doesn't get pushed back yet again (as
> it has for the last 2 years).
>
>> Right now there isn't an NSRegularExpression, and it looks like
>> there's more work necessary before we get one. So we can use one of
>> various third-party frameworks, or directly use one of various third-
>> party libraries.
>
> Yes, the same argument can be made for features like Source lists and
> Media Browsing. Just because there is a work around doesn't mean there
> shouldn't be a solution included in the current Cocoa frameworks.
>
> While there are 3rd party options, they aren't all consistent in their
> syntax and options. So any regexp exposed to the end user is subject
> to inconsistent behavior from their point of view. Having a common
> library supported by the OS helps eliminate that issue.






Cocoa mail archive

