Home > Archive > PHP PEAR Questions and Answers > March 2005 > Re: [PEAR-QA] entities in package.xml must be the Ӓ type or
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: [PEAR-QA] entities in package.xml must be the Ӓ type or
|
|
| Klaus Guenther 2005-03-01, 3:57 pm |
| On 3/1/2005 5:47 PM, Greg Beaver spake the following words:
> Note the most recent problem with I18n_v2
>
> Greg
>
> P.S. did I mention that I ****ing hate working with saxon across
> different PHP versions?
Can you switch to SimpleXML in php5 or do you need more indepth xml support?
Klaus
| |
| Klaus Guenther 2005-03-01, 3:57 pm |
| On 3/1/2005 6:13 PM, Justin Patrin spake the following words:
>On Tue, 01 Mar 2005 17:53:53 +0100, Klaus Guenther
><klaus@capitalfocus.org> wrote:
>
>
>This is PEAR we're talking about. Many people don't have SimpleXML and PHP5.
>
>
Yeah, which is why I'd suggest starting to switch over to php5, which
might make it easier in the future, when php5 is available. Which is why
I was suggesting implementing it dually - for php5 and php4, using sax
for php4 and maybe SimpleXML for php5. If it makes things easier than
cripling the installer by forcing an implementation that works in both
php4 and php5, I'm all for it.
Maybe it would even be best to create two versions of the installer -
php4 and php5, and depending on what is installed, it installs the
appropriate version. Of course, the di vantage would be if someone
upgrades to php5 and all of a sudden, the PEAR installer doesn't work
anymore. Maybe there could be an autoupgrade function for PEAR, simply
copying the appropriate scripts. It might be more work now to make a
dual implementation, but it might be very helpful next year. It might
even be easier for Greg than breaking his head over compatibility problems.
Anyway, that's just my two cents.
Klaus
| |
| Greg Beaver 2005-03-01, 3:57 pm |
| Klaus Guenther wrote:
> On 3/1/2005 6:13 PM, Justin Patrin spake the following words:
>
>
> Yeah, which is why I'd suggest starting to switch over to php5, which
> might make it easier in the future, when php5 is available. Which is
> why I was suggesting implementing it dually - for php5 and php4, using
> sax for php4 and maybe SimpleXML for php5. If it makes things easier
> than cripling the installer by forcing an implementation that works in
> both php4 and php5, I'm all for it.
>
> Maybe it would even be best to create two versions of the installer -
> php4 and php5, and depending on what is installed, it installs the
> appropriate version. Of course, the divantage would be if someone
> upgrades to php5 and all of a sudden, the PEAR installer doesn't work
> anymore. Maybe there could be an autoupgrade function for PEAR, simply
> copying the appropriate scripts. It might be more work now to make a
> dual implementation, but it might be very helpful next year. It might
> even be easier for Greg than breaking his head over compatibility
> problems.
>
> Anyway, that's just my two cents.
I spent about 3 months working on a simplexml-based solution to
package.xml parsing, and the short answer is that it is completely
impossible without breaking BC in a major way (read: php 4 PEAR can't
read php 5 registry, and vice-versa).
Greg
|
|
|
|
|