Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:38955
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 85.214.94.56 as permitted sender)
Date: Tue, 15 Jul 2008 13:32:05 +0200
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <95292873.20080715133205@marcus-boerger.de>
To: Moriyoshi Koizumi <moriyoshi@at.wakwak.com>
CC: internals@lists.php.net
In-Reply-To: <487C847F.7050302@at.wakwak.com>
References: <487C847F.7050302@at.wakwak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] --disable-mbregex in HEAD?
From: helly@php.net (Marcus Boerger)

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