I was just using the ability to remove mbstring from ext as a selling point to get the patch into PHP. Stays or goes is up to you guys. :-) What I am doing for work is setting up a bare PHP that can be installed on all server and then who ever needs mbstring, xml, xslt or what ever extension can just load that shared extension. This way you only load what you need and nothing you don't.
I haven't been able to get the session extension built as shared, any tips on that? Or the mysql for that matter. Yes adding --with-mysql=shared to PHP's configure builds a shared .so, but it is rather small compared to the one if you build it with phpize, ./configure, make in the ext/mysql directory. Thanks, Brian At 8:44 AM +0900 6/21/02, Yasuo Ohgaki wrote: >Brian France wrote: >>Ok, what does exif need from mbstring, code wise? Taking a look at >>it I don't see any references to mbstring in the code. >> > >exif needs mbstring to handle multibyte chars. > >IMO, removing mbstring from PHP is ok as long as user >knows what they are doing. We can remove other internal >modules, such as session module also. > >-- >Yasuo Ohgaki -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
