Hi! > I did mean would — one issue with much of our internationalisation > code is that it's in extensions (intl, iconv, mbstring) that are > inconsistently deployed by shared hosting providers. Having some basic
Shared hosting providers are completely capable of building their PHP offerings the way they want. Adding yet another - fourth? fifth? sixth? - way of doing string operations is not going to change anything. If the problem is hosting providers, it should be handled at that point, not in PHP core. > conversion and string handling functions that could be available in > ext/standard might not be a bad thing. Same argument would apply to any functionality that is useful for anybody - it all should be in ext/standard or some shared hosting provider could build PHP without it. Obviously, it's not a good argument, and if hosting provider does not provide common modules, choose another provider - there are hundreds of others just a simple search away. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
