this post was submitted on 27 Jul 2025
6 points (100.0% liked)

Hacker News

2340 readers
422 users here now

Posts from the RSS Feed of HackerNews.

The feed sometimes contains ads and posts that have been removed by the mod team at HN.

founded 11 months ago
MODERATORS
patrick@lemmy.bestiver.se
rssbot@lemmy.bestiver.se
6
Why I write recursive descent parsers (despite their issues) (utcc.utoronto.ca)
submitted 2 weeks ago by rssbot@lemmy.bestiver.se to c/hackernews@lemmy.bestiver.se
1 comments fedilink hide all child comments
 

Comments

you are viewing a single comment's thread
view the rest of the comments
[–] henfredemars 1 points 2 weeks ago* (last edited 2 weeks ago)

I strongly prefer recursive descent for parsers for a different reason: clarity. They are easy to read and they are easy to generate helpful error messages for the user because right there in the code of your parser you can provide great, contextually-relevant error messages.

I’ve tried parser generators a few times, but after running with the code for a while, it just doesn’t offer me the level of error reporting flexibility that I can achieve using a simple descent.