Re: can I depend on stable PEAR classes to not change?

On Tue, 24 Aug 2004 17:42:10 -0400, Greg Beaver <cellog@php.net> wrote: > > > Culley Harrelson wrote: > > > 1) s/require_once 'HTML/QuickForm.php'/require_once 'MyQuickForm.php' > 2) s/new HTML_QuickForm/new MyQuickForm > > voila. not voila. QuickForm3 introduced renderers. If you were using Quickform2 methods setElementTemplate() and addData() to significantly customize your output then a couple of substitution commands isn't going to bail you out. > > If you plan to use PEAR, you must plan to either use moldy old packages, > or adapt to the future. PHP is the same way. You could still use moldy > php3 applications, or you could redesign to take advantage of php5. It > all takes work, perhaps you should consider taking up something less > dynamic than programming, like accounting ;). Of course, tax law is > constantly changing and so I guess even that isn't so static... This sounds like a weak excuse for library authors to screw with the API. I am self employed, writing applications in php that pay my mortgage and feed my kids. My livelihood depends on the stability of the libraries I use. I have a 1500 line todo list and *no* time to go back and rewrite code because a library has changed it's api. I want to rewrite code when my business changes and that is it. When I have to rewrite code because the library API changes I see it as an indication that I chose the wrong library to use in the first place. Whoops! culley