Hi there,
(Yeah, it's been a long time.. Many of you might well have thought
I'm dead :)
This time I want to revisit the following issue:
http://article.gmane.org/gmane.comp.php.devel/50681
Is there any point to disable mbregex alone instead of disabling the
whole mbstring stuff? Unless the decision whether to send the module into
PECL (or anywhere you want it to go) has been made, I suppose it should
not.
Regards,
Moriyoshi
Hello Moriyoshi,
Tuesday, July 15, 2008, 1:05:35 PM, you wrote:
Hi there,
(Yeah, it's been a long time.. Many of you might well have thought
I'm dead :)
This time I want to revisit the following issue:
http://article.gmane.org/gmane.comp.php.devel/50681
Is there any point to disable mbregex alone instead of disabling the
whole mbstring stuff? Unless the decision whether to send the module into
PECL (or anywhere you want it to go) has been made, I suppose it should
not.
(just for Derick answered here)
I never liked this. So imo we can simply get rid of this switch and enable
mbregex as soon as there is mbstring to begin with and regex stuff.
Best regards,
Marcus
Marcus Boerger wrote:
Hello Moriyoshi,
(just for Derick answered here)
I never liked this. So imo we can simply get rid of this switch and enable
mbregex as soon as there is mbstring to begin with and regex stuff.
Me neither. As far as I know, the switch exists just for historical
reasons. Since --enable-mbregex takes effect only when --enable-mbstring
is specified, it'd be the same as if there was the single option.
Aside from this, what about removing bundled libmbfl and oniguruma from
HEAD and requiring users' using external ones? Now that intl extension
was merged and I don't think it makes sense.
Regards,
Moriyoshi
Hello Moriyoshi,
Tuesday, July 15, 2008, 4:58:38 PM, you wrote:
Marcus Boerger wrote:
Hello Moriyoshi,
(just for Derick answered here)
I never liked this. So imo we can simply get rid of this switch and enable
mbregex as soon as there is mbstring to begin with and regex stuff.
Me neither. As far as I know, the switch exists just for historical
reasons. Since --enable-mbregex takes effect only when --enable-mbstring
is specified, it'd be the same as if there was the single option.
Aside from this, what about removing bundled libmbfl and oniguruma from
HEAD and requiring users' using external ones? Now that intl extension
was merged and I don't think it makes sense.
Would be fine with me as well.
Best regards,
Marcus
Aside from this, what about removing bundled libmbfl and oniguruma from
HEAD and requiring users' using external ones? Now that intl extension
was merged and I don't think it makes sense.
Huge ++ from me, especially regarding oniguruma. If you'd want to make
it optional (but not required), I've sent a related patch to this list
weeks ago.
--
Christian Hoffmann