On 16/07/12 08:04, Galen Wright-Watson wrote: > What about an approach like PDO, where the password functions would > generate errors by default, but could be configured to throw exceptions? > The ugliest aspects of this idea are the requirement for another function > (password_set_option?) and hidden state. On the plus side, if you stick > with errors for now it could be implemented down the road and be fully BC. PDO lets you set it per pdo object. In this case you would be manipulating a global. Which means integrating a new password module (for a shared login between different installed appplications) they could be warring on that option.
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
