sniper Fri Mar 25 22:13:58 2005 EDT
Modified files:
/php-src/ext/xmlcompat.c expat_compat.h
/php-src/ext/xmlrpc config.m4
/php-src/ext/xmlrpc/libxmlrpc xml_element.c xmlrpc.c
/php-src/main php_compat.h
Log:
- Made it possible to
chregu Sun Feb 22 12:51:02 2004 EDT
Modified files:
/php-src/ext/xmlcompat.c expat_compat.h
Log:
Fix broken Namespace support, use libxml2 namespace methods instead of
homebrown solution:
- default namespaces are recognized
- different namespaces with
What version of libxml2 does this rely on?
-Sterling
chreguSun Feb 22 12:51:02 2004 EDT
Modified files:
/php-src/ext/xml compat.c expat_compat.h
Log:
Fix broken Namespace support, use libxml2 namespace methods instead of
homebrown solution:
Hi
mmmh, forget about that... I used 2.6.2, will test on 2.5.10 later
chregu
On 2/22/04 6:55 PM, Sterling Hughes wrote:
What version of libxml2 does this rely on?
-Sterling
chregu Sun Feb 22 12:51:02 2004 EDT
Modified files:
/php-src/ext/xml compat.c expat_compat.h
Log:
On Sun, 22 Feb 2004, Christian Stocker wrote:
mmmh, forget about that... I used 2.6.2, will test on 2.5.10 later
I think SAX2 support began with 2.6.0, but maybe you can enable SAX 1
usage for older version?
-adam
--
[EMAIL PROTECTED]
author of o'reilly's php cookbook
avoid the holiday rush,
This change requires libxml 2.6 in order to work (and compile).
Rob
On Sunday 22 February 2004 01:05 pm, Christian Stocker wrote:
Hi
mmmh, forget about that... I used 2.6.2, will test on 2.5.10 later
chregu
On 2/22/04 6:55 PM, Sterling Hughes wrote:
What version of libxml2 does this
Mmmh
too bad, will try to find a solution for libxml2 2.6
I know, it's late in the release process, but the old implementation
didn't recognise default namespaces, which broke quite some ext/xml
scripts from php4 days and I'd like to have fixed that before 5.0.0
chregu
On 2/22/04 7:34 PM,
Mmmh
too bad, will try to find a solution for libxml2 2.6
I know, it's late in the release process, but the old implementation
didn't recognise default namespaces, which broke quite some ext/xml
scripts from php4 days and I'd like to have fixed that before 5.0.0
In the meantime
On Sunday 22 February 2004 01:36 pm, Sterling Hughes wrote:
Mmmh
too bad, will try to find a solution for libxml2 2.6
I know, it's late in the release process, but the old implementation
didn't recognise default namespaces, which broke quite some ext/xml
scripts from php4 days and
Ok
there are 5 different solutions now to this problem
1) fix the code, so that it works with 2.5.x correctly as well
2) make 2.6.x a prerequisite
3) disable xml_parser_create_ns for 2.5.x
4) use broken code for 2.5.x and fixed code for 2.6.x
5) revert to yesterdays situation (broken for all...)
At 14:10 22/02/2004 -0500, Rob Richards wrote:
On Sunday 22 February 2004 01:36 pm, Sterling Hughes wrote:
Mmmh
too bad, will try to find a solution for libxml2 2.6
I know, it's late in the release process, but the old implementation
didn't recognise default namespaces, which broke
Ok
there are 5 different solutions now to this problem
1) fix the code, so that it works with 2.5.x correctly as well
2) make 2.6.x a prerequisite
3) disable xml_parser_create_ns for 2.5.x
4) use broken code for 2.5.x and fixed code for 2.6.x
5) revert to yesterdays situation (broken
Hello Christian,
Sunday, February 22, 2004, 11:59:34 PM, you wrote:
Ok
there are 5 different solutions now to this problem
1) fix the code, so that it works with 2.5.x correctly as well
2) make 2.6.x a prerequisite
3) disable xml_parser_create_ns for 2.5.x
4) use broken code for 2.5.x
1) fix the code, so that it works with 2.5.x correctly as well
2) make 2.6.x a prerequisite
3) disable xml_parser_create_ns for 2.5.x
4) use broken code for 2.5.x and fixed code for 2.6.x
5) revert to yesterdays situation (broken for all...)
I prefer 3. simply add some
It will never work correctly for option 1. Namespaces in SAX was a 2.6
thing
(SAX2).
Right, but namespaces just need to work as good as they did in PHP4, we
can't lose that compatibility. If it works better - bonus.
So what exactly is broken then in comparison to PHP4? From the size of
It will never work correctly for option 1. Namespaces in SAX was a 2.6
thing
(SAX2).
Right, but namespaces just need to work as good as they did in PHP4, we
can't lose that compatibility. If it works better - bonus.
So what exactly is broken then in comparison to PHP4? From the
On 2/23/04 1:53 AM, Sterling Hughes wrote:
It will never work correctly for option 1. Namespaces in SAX was a 2.6
thing
(SAX2).
Right, but namespaces just need to work as good as they did in PHP4, we
can't lose that compatibility. If it works better - bonus.
So what exactly is broken then in
At 19:25 22/02/2004 -0500, Rob Richards wrote:
How much time we looking at between RC1 and a final release?
I'd guesstimate a couple of months, around May.
Andi
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On Sun, 22 Feb 2004, Rob Richards wrote:
I'm fine with requiring 2.6, although things could blow up.
Right, that is what I am afraid of as well. As I mentioned I can live with
it, but prefer not to do this.
I've been running with 2.6 since it was out... no weird problems here
(but I don't
wez Fri Dec 19 11:57:37 2003 EDT
Modified files:
/php-src/ext/xmlcompat.c expat_compat.h
Log:
Export expat compat functions.
Implement XML_GetCurrentByteCount(); probably not 100%
correct, but the only usage of it is by xmlrpc extension when
rrichards Mon Sep 29 07:35:40 2003 EDT
Modified files:
/php-src/ext/xmlexpat_compat.h compat.c
Log:
fix for bug #25666 (XML namespaces broken in PHP5)
Index: php-src/ext/xml/expat_compat.h
diff -u php-src/ext/xml/expat_compat.h:1.12
21 matches
Mail list logo
