<?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 ilikeorangutans</title><link>https://kuelzer.ca/tags/parser/</link><description>Recent content in Parser on ilikeorangutans</description><generator>Hugo</generator><language>en</language><copyright>© 2026 Jakob Külzer</copyright><lastBuildDate>Sun, 12 Apr 2026 14:27:24 -0400</lastBuildDate><atom:link href="https://kuelzer.ca/tags/parser/index.xml" rel="self" type="application/rss+xml"/><item><title>Antlr Grammars for Fun and Profit</title><link>https://kuelzer.ca/posts/2010/11/24/antlr-grammars-for-fun-and-profit/</link><pubDate>Wed, 24 Nov 2010 23:10:35 -0400</pubDate><guid>https://kuelzer.ca/posts/2010/11/24/antlr-grammars-for-fun-and-profit/</guid><description>&lt;p&gt;Recently at work I had to work on files in our legacy system. Those files, being part of a proprietary product, are unknown to any editor or pretty printer that you can find. And most of them are not formatted nicely, if at all. Being a lazy developer I really love eclipse&amp;rsquo;s code formatting features, because, hey, it takes away a lot of tedious and annoying formatting. Also, I think properly formatted files are easier to understand, maintain and fix. In fact, as I recently tweeted, I go as far as saying that I&amp;rsquo;m not particularly good in spotting problems, I just format everything which helps me to understand better.&lt;/p&gt;</description></item></channel></rss>