That's a bit hair splitting but, for me parsing is more about reconstructing the structure from a flattened representation. I even dig a supporting online definition:
parse:
1. To determine the syntactic structure of a sentence or other utterance
And here he does not need to think about the structure - all he needs is that the needed information is just after and just before some specified strings.
Following the structure of the document is usually more general way of searching the needed information, because it is more formally defined, but sometimes you don't need to do that since you know about other properties of the data that can lead you to your goal (and sometimes you don't know much about the structure of the document).
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.