Re: BC breakage results

<rob.hutton@comcast.net> wrote : > Even if NOTHING that depends on QuickForm in PEAR (all we know about is what > is in PEAR, not what the users have done), then the API should still be > available until 4.0. Be it via some sort of compatability setup, or > whatever. Deprecating them inside of a subrelease, OK. Returning errors or > removing them, BAD. Just as a sidenote : There are multiple levels of errors available : warnings, notices... They should be treated differently by the user. For example, AFAIR, in PHP if you use setlocale('LC_ALL', 'fr_FR') it will issue a warning telling you setlocale now expects the user to use the locale constants (LC_ALL instead of 'LC_ALL'). Still, the function does the job. I have decided to follow this behaviour in HTML_QuickForm 3.1 because it helps users find deprecated methods in their code. I use HTML_QuickForm a lot in my apps and it's sometime hard to remember where the deprecated code is. Now, using a some error log function as PEAR Error handler, it makes it easier to find the faulty piece of code. The error log function can be prepended using auto_prepend for a week or two. Maybe that's not the best solution... Bertrand Mansion Mamasam