Re: Forking PEAR

Ok, I'm not going into detail, just saying this: excellent idea! Hans' reply showed what I first thought when I read Heino's thoughts, again there will be a split between PHP4- and PHP5-oriented users. People favoring PHP4 won't like the idea, peopl favoring PHP5 will love it. I'm developing a large-scale, completely oo-designed, project which started a long time ago in PHP4. It relies on several (7 or 8) PEAR-packages, but when the first PHP5-RC came out the first thing I did was migrate the whole project in several weeks to PHP5. The new Object-Model is really a great relieve when doing a project without any procedural code (Ok, there is one procedural line *g*). Now I have the problem with E_STRICT, MY code is E_STRICT-compliant, all of the other PEAR-packages are not. Makes development really hard. I use exceptions (I'm coming from big java-projects, so they are well-known for me), and I don't want to miss them anymore. But on the other hand I don't want to miss the excellent PEAR-packages, but it would be great to have most of them PHP5-compatible. I think with PHP5 a lot of users will come from other languages, people that developed java-webapps, for example. What use will have PEAR for some? Not really any use. Having PHP4 packages converted to PHP5 in another channel would be the solution, the maintainers can still develop whatever version they want, someone else could do the conversion. And if it's only a conversion to keep it E_STRICT compatible for PHP5, who cares? As long as everybody is served... Anyone know the story about the 8086 A20-gate? Hope PEAR won't do the same errors... Stephan