Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:22855 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 89091 invoked by uid 1010); 19 Apr 2006 11:34:31 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 89076 invoked from network); 19 Apr 2006 11:34:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Apr 2006 11:34:31 -0000 X-Host-Fingerprint: 212.55.154.24 relay4.ptmail.sapo.pt Linux 2.4/2.6 Received: from ([212.55.154.24:36031] helo=sapo.pt) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 58/61-19715-64026444 for ; Wed, 19 Apr 2006 07:34:30 -0400 Received: (qmail 6037 invoked by uid 0); 19 Apr 2006 11:33:02 -0000 Received: from unknown (HELO sapo.pt) (10.134.35.155) by relay4 with SMTP; 19 Apr 2006 11:33:02 -0000 Received: (qmail 9135 invoked from network); 19 Apr 2006 11:34:27 -0000 X-AntiVirus: PTMail-AV 0.3.88 X-Virus-Status: Clean (0.00680 seconds) Received: from unknown (HELO pc07653) (nunoplopes@sapo.pt@[81.193.156.122]) (envelope-sender ) by mta5 (qmail-ldap-1.03) with SMTP for ; 19 Apr 2006 11:34:27 -0000 Message-ID: <000701c663a5$35558ab0$0100a8c0@pc07653> To: "Steph Fox" , "internals" Cc: "Edin" References: <09f201c6639c$c8fe39f0$6602a8c0@foxbox> <0a0a01c663a0$755b4230$6602a8c0@foxbox> <008b01c6639d$f39177d0$0100a8c0@pc07653> <0a1f01c663a6$f49711e0$6602a8c0@foxbox> <00a201c6639f$bee582e0$0100a8c0@pc07653> <0a4301c663ac$9cc9bf70$6602a8c0@foxbox> Date: Wed, 19 Apr 2006 12:34:23 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Subject: Re: [PHP-DEV] tiny patch for Tidy From: nlopess@php.net ("Nuno Lopes") >> >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