<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Parser on Joe Bylund</title><link>http://jbylund.github.io/tags/parser/</link><description>Recent content in Parser on Joe Bylund</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Joe Bylund</copyright><lastBuildDate>Tue, 07 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://jbylund.github.io/tags/parser/index.xml" rel="self" type="application/rss+xml"/><item><title>Whitespace as an Operator: Parsing Scryfall's Implicit AND</title><link>http://jbylund.github.io/posts/00112_implicit-and-query-balancing/</link><pubDate>Tue, 07 Jul 2026 00:00:00 +0000</pubDate><guid>http://jbylund.github.io/posts/00112_implicit-and-query-balancing/</guid><description>The Scryfall query language implicitly ANDs adjacent terms — pyparsing does not. This post covers the preprocessing layer built on top: implicit AND injection, query balancing in two languages, and the edge cases that required fixes.</description></item><item><title>Choosing a Parser for a Query DSL: Regex, ANTLR, Lark, and pyparsing</title><link>http://jbylund.github.io/posts/00096_query-dsl-with-pyparsing/</link><pubDate>Fri, 03 Jul 2026 00:00:00 +0000</pubDate><guid>http://jbylund.github.io/posts/00096_query-dsl-with-pyparsing/</guid><description>How I evaluated parsing approaches for Scryfall&amp;rsquo;s query language: why regex and ANTLR were ruled out, how Lark compares to pyparsing, and why pyparsing won.</description></item></channel></rss>