In the primary use of tidy (which is to validate HTML), there is very little need for a returned resource other than to clutter the namespace. Unlike most extensions, where it would be useful imo the resource is unnecessary. Since we can reuse the container for the tidy documentation, it's much faster to just perform serial operations for the general case then it is to reallocate a brand new container every time for no reason.
As far as the API itself goes for the OO side of things, I think the API that is exposed is just fine. Just as is the case with any screen-scraping tool, the problem is not in the tool but in the document you are scraping (trying to find that table you want buried in the document). John On Mon, 2003-12-01 at 12:46, Thies C.Arntzen wrote: > before bundling i'd like to see the api refined... > > right now it's not possible to work with more than one html-doc at a > time. (tidy_parse_file() does not return a resource to the internal > tidy doc, so you can only have one doc at a time) > > also we should ask ourself if (i haven't used tidy so i might be wrong) > we want tidy to expose a similar API as SimpleXML does (which we all > seem to like - be it too magic or not) > > re, > tc > > > Am 01.12.2003 um 18:39 schrieb Georg Richter: > > > > >> I would like to propose that tidy extension be bundled with PHP 5. > > > > +1 > > > > Georg > > > > -- > > PHP Internals - PHP Runtime Development Mailing List > > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
