Re: an HTML_Template_IT[X] fork is available

> On Wed, 12 Feb 2003 01:10:32 +0300 > Alexey Borzov <borz_off@cs.msu.su> wrote: > >> Christian Dickmann wrote: >> > We don't have to prove, that your new package breaks BC, >> > you have to prove, that it does not! >> >> This is a *perfect* example of faulty logic. >> >> Consider: I don't have to prove that the world was created just >> yesterday by The Great Almighty Foobar. You have to prove that it was >> not! > > > To go back on topic: IT[X] is a package that is used in countless > application, some that have been around for years. The old version has a > majority of users behind it who will claim that it works with their > apps. Therefore, it´s again your turn to prove that the new theory is > true. > > Post a link to your class, please. I will test it with one of my apps > and tell you the outcome. But as I don´t use the more sophisticated > features of IT[X], that still doesn´t prove a thing. You´ll need more > and you can´t possibly know and test all apps that use it. A dilemma. > > On the other hand, proof is not really the point here - any application > developer is free to keep using the old version. And if that works for > him, why shouldn´t he? I tend to bundle a specific version of PEAR > classes with my apps anyway to prevent some system administrator to > break my app by upgrading to a newer PEAR version that will break BC - > and I would advise any other developer to do the same. I do the same, since i dont trust my code enough actually to go through 100+ revisions of valid pear code and not become buggy... The only disadvantage I see with this is that if something important is fixed in Pear, i will have to figure out a way to introduce the fix into my app specific version of Pear. Another thing, isnt it a good idea to introduce unit testing into pear classes, so you could 'just' run the unittest against a newer version of a class, be it a rather complete rewrite, be it a minor patch.. If the unit tests are written correctly, and people still have bc breakage, its due to their misunderstanding of the class, and then the idea of delivering a specific version of pear(classes) with your app is a good solution again.. regards, Maarten