Re: IT[X] unstable - why?

Alexander Merz wrote:

I wrote this manual entry and i never called ITX unstable. The problem with ITX is: a) no maintainer b) ITX is *not* 100% PHPLib template compatible, but a lot people believe this c) We have IT and Template_PHPLib, both are working fine. ITX is a bastard, a thing between, which have never go to the PEAR repository. ITX sets a layer over a layer -> slower then every other template solution in PEAR. There is no real reason to use it.

Hmm. As i said: IT[X] inherits most of it's functionality from IT. There are only a few methods added to add a block from a file and some callback stuff. Everything else is absolutely identical to / inherited from IT. Personally i've missed exactly the blockfile feature in IT. So is it really such a performance killer in PHP to use an extended class? If so, maybe one could merge the IT[X] functionality into IT. I really can't see any other point why IT[X] should be less usable than IT. To put it another way: if IT[X] is not usable, IT can't be either, since they share nearly all of their functionality. Michael P.S.: As stated once, i could take over maintainership for IT[X], but as long as noone sees a point in having it in PEAR, well ...