<shrug />
It seems very odd to me there can't just be a one-line fix for something
that's broken in 5_1 win32 static build without a whole hoo-ha going down.
The extension doesn't build against the new library without fiddling, and
nor does it build against the library we actually use. The difference is
that if the new library is used in the distro builds it _may_ affect the PHP
4.* version (did anyone test to prove it won't, yet?), and _will_
(definitively) affect anyone attempting to build the extension against an
older copy of the library, thanks to a minor API change in Tidy.
On the other hand, if the extension is fixed in PHP 5.1 and up to build with
the existing library, it will _only_ affect win32 users attempting to build
the extension statically against a newer edition of the library - which they
can't currently do anyway.
So what's the issue?
- Steph
Something's odd in the manual then:
Note: Tidy 1.0 is just for PHP 4.3.x, while Tidy 2.0 is just for PHP 5.
Which refers to ext/tidy version (AFAICT).
Regards,
--
Michael - <mike(@)php.net>
http://dev.iworks.at/ext-http/http-functions.html.gz
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
