RE: [PHP-DEV] Re: mbstring

> -----Original Message----- > From: derick@php.net [mailto:derick@php.net] > Sent: Tuesday, September 03, 2002 7:51 AM > To: James Cox > Cc: Rui Hirokawa; php-dev@lists.php.net > Subject: RE: [PHP-DEV] Re: mbstring > > > On Tue, 3 Sep 2002, James Cox wrote: > > > > > > > No, this option is 'disabled' by default, and can be enabled by a > > > ini variable. > > > > > > mbstring.encoding_translation = Off; is default. > > > > > > If mbstring.encoding_translation = On is set in php.ini, > > > the transparent conversion will be enabled. > > > > > ok, but before, you had to --enable it before it'd work? or did > it get built > > _EVERY_ time regardless? > > Does it matter? ini settings are much easier to notice during debugging > than #ifdefs, so I think Rui made an excellent choice here. However, > some documentation of these settings would be useful (hint :). > well, the mbstring-enc-trans stuff is what seems to have caused the issues before, so having it built in might not be a great idea. Besides, it just increases the base binary size, which makes life harder for people trying to embed php. > > > > [snip] > > > Yes, I think mbstring is very fundamental feature and it should > > > be built-in > > > feature (in PHP 5.0). > > > But, string related functions and some other core functions > > > are included in ext/standard which is also in extension part. > > > > > > > sure, ext/standard works... we just need to lose the duplication. > > You obviously have no idea what mbstring exactly does, as this comments > makes little sense. mbstring _overloads_ functions which are in > ext/standard (such as strpos() ). That is a little bit too much magic, > and thus I like to see the mbstring functions merged into the > ext/standard functions (for PHP 5). > Sorry, that's what i meant: to move ext/mbstring overloading stuff into it's rightful place, rather than duplicating the code.