in reply to Re^3: use strict and TokeParser
in thread use strict and TokeParser

Sorry for the late reply. Yes, that is a bug report in HTML::LinkExtractor (my module). That bug was caused by (at that time) latest version of HTML::TokeParser::Simple. I hastily got rid of HTML::TokeParser::Simple, uploaded a new version of my module and forgot about it until my reply above (sorry if Instead of trying to figure out what was broken in HTML::TokeParser::Simple was vague).

It happens sometimes, I should've been more verbose.

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

Replies are listed 'Best First'.
Re^5: use strict and TokeParser
by Ovid (Cardinal) on Jun 03, 2005 at 15:39 UTC

    No problem. If you happen to recall the bug and can tell me the steps to reproduce it, I'll be happy to fix it and add a test.

    Cheers,
    Ovid

    New address of my CGI Course.

      Using HTML::LinkExtractor v.11 from backpan, and the bug previously mentioned, I reproduced the bug, and could not find anything wrong with HTML::TokeParser::Simple(v3.13). I did however find this in HTML::LinkExtractor:
      ## In case we got nested tags if(@TEXT) { $TEXT[-1]->{_TEXT} .= $T->as_is; }
      I have some idea of what the purpose of the code above was, but it had the effect of setting the current "text" of the link (even the top level non-nested link tag since the @TEXT array was non-empty and the _TEXT contained an empty string) to the entire <a href="..."> tag (and then later the actual text is appended).