[pcre-dev] [Bug 2294] pcregrep -E

トップ ページ
このメッセージを削除
著者: admin
日付:  
To: pcre-dev
題目: [pcre-dev] [Bug 2294] pcregrep -E
https://bugs.exim.org/show_bug.cgi?id=2294

Philip Hazel <ph10@???> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WONTFIX
             Status|NEW                         |RESOLVED


--- Comment #7 from Philip Hazel <ph10@???> ---
(In reply to Elliott Hughes from comment #6)

> yeah, maybe you're right. certainly the BRE/ERE behavior is going to matter
> to far more people (and their scripts) than -P. so if PCRE can't give exact
> BRE/ERE semantics this seems like it's doomed to failure. in which case i'll
> go back to my original plan of sticking to BSD grep until toybox grep gets
> to the point where we can switch to that.


I think that is best, but it's probably useful to have explored this issue.
>
> on the good news front, i've updated AOSP master to PCRE 10.31.


Very shortly, in a few weeks, I will have to start pulling together a 10.32
release candidate. There is a slow trickle of changes and bug fixes.

> (insert grumble here about there not being a -announce@ mailing list for me
> to subscribe to, nor a github mirror that would let me programmatically
> query for new releases...)


I'm an old dog that takes time to learn new tricks, and I'm afraid I have never
got round to learning Git. PCRE was set up with SVN just over 20 years ago, and
I've just stuck with it. As for -announce, nobody has asked for it, until now.
I guess they all manage with the pcre-dev list, which isn't hugely busy.
Perhaps I should ask on the list if such a thing would be popular - and if so,
persuade the exim.org managers to set it up. (I've always relied on other folks
to do everything except work on the code, e.g. website, mailing list, etc.
Can't do everything myself...)
>
> thanks for your time though!


No problem. Thinking through this kind of thing often generates useful insights
and peripheral ideas. I will now close this bug. "Invalid" isn't quite right,
so I'll go for "wontfix".

--
You are receiving this mail because:
You are on the CC list for the bug.