At 01:24 02.09.2002, Yasuo Ohgaki wrote: >Brian France wrote: >>I know there are things the exif needs from mbstring and there is no way >>to have exif link against mbstring or require it. But couldn't exif >>check to see if mbstring is loaded (or built in) and if not print a >>warning that some of its functionality may not work correctly unless >>mbstring is loaded (or built in)? > >It's not a good idea. > >What we need is smart ini parser and module loader that understand >module dependecy and proper loading order.
PLEASE charme down on exif/mbstring liaison. ext/exif is by now the most capable implemetnation available freely (with the restriction that it can only read things) so i guess i can invent some workaround. Or the users who really like that liaison can enable both modules. For me the only reason to depend on both is the combination of ACDSee and php. More will follow but i hope until then mbstring/I18n is fully integrated in php5.0. So my vote is +1 for having I18n support for php by mbstring being default. AND exif has no affect. It works whether or not mbstring is there. Just some tags might cause some problems (WinXP specific and one more). AND exif is disliked by the developers on this list so why do we care now? -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
