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?
BTW, the libtidy could be updated :) It had a major optimization a few
time ago (it decreased my bechmark running time by ~30%).
Nuno
----- Original Message -----
From: "Steph Fox" <[EMAIL PROTECTED]>
To: "internals" <internals@lists.php.net>
Cc: "Edin" <[EMAIL PROTECTED]>
Sent: Wednesday, April 19, 2006 12:00 PM
Subject: Re: [PHP-DEV] tiny patch for Tidy
Oops, forget it. The problem with having both PECL and src on board is I
assumed I was building against the one with this change in it. I wasn't -
I was building against the one that didn't have tidyOptGetDoc in the
export list AT ALL.
Just ran a test and found this is illegal syntax :( so back to the
drawing board.
(Edin: is there some way you know of to do an #ifdef equivalent in these
export lists?)
- Steph
----- Original Message -----
From: "Steph Fox" <[EMAIL PROTECTED]>
To: "internals" <internals@lists.php.net>
Sent: Wednesday, April 19, 2006 12:34 PM
Subject: [PHP-DEV] tiny patch for Tidy
This allows static builds under win32 despite the fact that
tidyOptGetDoc()
doesn't exist in the libtidy.lib we're linking against.
It needs applying to php_tidy.def everywhere libtidy v 2 is used - that
is,
ext/tidy in CVS HEAD and PHP_5_1, and CVS HEAD pecl/tidy.
In all three cases there is the same #ifdef clause for the matching
tidy_get_opt_doc() function in the header file.
- Steph
__________ NOD32 1.1380 (20060125) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
