Bug #722 Updated: setlocale: scanner (scanf?) / printf don't work properly

ID: 722 Updated by: jaakko Reported By: vogtner@soldan.de Status: Assigned Bug Type: Misbehaving function Assigned To: jaakko Comments: True, this should not happen. But which is better: 1) Call setlocale in user function implementations and immediately revert back to "C" locale, or 2) protect PHP internal uses of functions which are affected by setlocale, by first setting locale to C and the reverting back to saved locale. 1) means setlocale() php function just saves the last setting for each category, and each user function calling affected code calls setlocale for it's own category with the saved value. This means we'll have to find those functions. 2) means no saved global state, but the setting for each category is saved just for the time the internal use of locale-affected function takes. This means we'll have to find all those places. I guess 2) is more work and might create a mess, but 1) introduces global state. Full Bug description available at: http://ca.php.net/bugs.php3?id=722 -- PHP Development Mailing List http://www.php.net/ To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net For help: php-dev-help@lists.php.net