The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I mean, it's not so much feeling bad, but knowing I can improve it, seeing as how i think my hand written parser is faster right now too thought it really should be *at least* as slow.
Or maybe i'm just expecting too much of it. Unlike PCK it can't stream - because it's recursive descent!, so it has to parse the entire stream into memory before you can have it.
The lag time sucks for large documents. With PCK i was never sure how "fast" it was, because it would start spitting nodes at me instantaneously - it streamed - it was a pull parser generator so it made parsers like Microsoft's XmlReader interface. When building the tree there was lag though, but it was a separate process in PCK. In Parsley it's integrated to the parse. Hard to profile each individually but not impossible.
Unfortunately, I can't generate FIRSTS(k) and FOLLOWS(k) sets for k>1 - I just don't know how and can't figure it out though i read a research paper that gave me an idea, i have yet to try it.
Then *maybe* with a table driven parser i could parse C#, but so far what i've seen of antlr, it can't do it.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
I whish you that the best of 2019 is the worst of 2020.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.