>I updated my copy from Edin's collection last week. It's newer than last
>year's, but I'm struggling to find any form of 'version' in there to
>know exactly what I have in front of me. So what are you talking about?
>Update from what, to what, and for which PHP build?
I'm talking about the libtidy version:
php -r "echo tidy_get_release();"
or
php -i | grep libTidy
the official php build's libtidy version is '1st July 2004', which is
almost two years old, and thus doesn't have the tidyOptGetDoc() function.
Heh, I never thought of that - I was looking through the source for an
actual version number, y'know, some API no or whatever. Something
normal...
Really this is down to John Coggeshall (as maintainer) - unless someone
else feels like going and finding a newer version of libtidy and testing
it with the existing extension(s) - e.g. would a newer version also bring
other new functions that aren't wrapped in the extension(s) currently?
I do really follow the libtidy development closely. I have the latest cvs
version installed on my pc and it runs correctly. All libtidy's tests run
fine and my own tests/benchmarks also run correctly.
And I don't remember any other function beeing added to libtidy lately. The
last one was that tidyOptGetDoc(), which is already exported.
In the meantime, we're building against this July 1st 2004 version - and
as I wrote earlier, that export file is _only_ used with the static win32
build. Surely we can allow that build to work with the lib used in the
official distro while we're waiting for whatever needs to be done for the
upgrade?
- Steph
Upgrading libtidy is five minutes (including download time..). Edin? :)
Nuno
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php