Re: Re: Will the QuickForm API always be a moving target?

<culley@fastmail.fm> wrote : >> Deprecated methods are easy to find in QuickForm.php source as they have >> been marked as such along with an explanation on how to get rid of them. >> > My question was malformed. What I meant to ask was are the depreciated > methods going to be completely removed from QuickForm? Yes, in the next release (3.2). So 3.1 might be the right version to get rid of the deprecated methods. >> I can understand your point of view as I have the same problems with my own >> code... That's why I have added these QUICKFORM_DEPRECATED errors, so that >> it's easier to find where deprecated methods are being used and fix my code. >> Personally, I log all the errors in a text file and correct them when they >> appear. 3.1 should be used as a transitional version. >> > I have a similar logging process. I could modify my error handler to > account for these errors-- errors of this level currently halt the > processing in my system. A warning is not a notice, it might be wise not to let them halt your processing, but that really is up to you. > Unfortunately I would need to modify and test > about 70 different forms to convert the depreceiated methods. Very > wasteful for someone with 2-3 years worth of work on their todo list. You can maybe use auto_prepend. There is not that much to change and we have tried to make it easy as much as possible. Bertrand Mansion Mamasam