<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ordered Context-Free Grammars Revisited · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2309.08717/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2309.08717/feed.xml" rel="self" type="application/rss+xml" /><item><title>Ordered Context-Free Grammars Revisited — mentioned by orlp</title><link>https://news.ycombinator.com/item?id=40583671</link><guid isPermaLink="false">urn:hackerpapers:mention:2309.08717:40583671</guid><pubDate>Wed, 05 Jun 2024 11:31:30 GMT</pubDate><description>&lt;p&gt;&amp;gt; The ordered choice operator should try all choices, not stop earlier. PEGs made this choice to ensure linear-time parsing. Another example of what I would consider a failure is the PEG grammar: Keyword = &amp;quot;else&amp;quot; / &amp;quot;elseif&amp;quot; This will only match &amp;quot;else&amp;quot;, it will never match &amp;quot;elseif&amp;quot; as the ordered choice will refuse to turn the successful match of &amp;quot;else&amp;quot; into a failure to try the &amp;quot;elseif&amp;quot;. &amp;gt; So I insist, you are using an incorrect parsing tool. I agree that PEG is an incorrect formalization for parsing, as it has highly unintuitive and surprising behaviors like this one. However, I have to…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2309.08717/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.FL</category></item></channel></rss>
