The problem is that you're trying to use the tool in a way it can't be used. Consider the following process instruction:

<?
    echo 'This is from PHP.';
?>

[download]

That runs over three lines. However, if you're reading things in line-by-line, you lose all context. When HTS gets to an individual line, it can't parse it as a process instruction because it doesn't know that it is one. I'm afraid you'll have to take a different approach to solving your problem.

I'm not sure there is a way around this problem, frankly, because the tokens will never have a direct correlation with line numbers. One possibility would be to (forgive me!) track the number of line endings in all tokens as a rough heuristic of which line a token is on.

Cheers,
Ovid

New address of my CGI Course.

In reply to Re: File parsing with HTML::TokeParser::Simple by Ovid
in thread File parsing with HTML::TokeParser::Simple by THRAK

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.