|
|
"Kenneth" <kdw### [at] gmailcom> wrote:
For single-line // comments, though, I would have imagined
> that all the text on that particular line would BE ignored, as soon as the
> parser came across a double slash // Hmm, apparently not.
I think I initially had that impression, but if you think about it, the parser
has to look for a NL/CR line ENDING character so that it knows what the next
line is.
Why this is so SLOW for the parser to do remains puzzling to me, since I can
download hundreds of megabytes, use FIND to search 1000+ page PDF's for text, or
search a whole directory or drive to find that text, and I have a positively
insane spreadsheet I wrote at work which does I don't even want to think about
how many _calculations_ .....
Maybe it's just old, horribly outdated / outmoded coding of the parser.
<Gollum> Clipka hates the parser, yes he does, my Precioussssssss <Gollum>
Post a reply to this message
|
|