<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Posts on blinx</title>
    <link>https://acctress.uk/posts/</link>
    <description>Recent content in Posts on blinx</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 05 Apr 2026 23:11:51 +0100</lastBuildDate>
    <atom:link href="https://acctress.uk/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Nature of Notation</title>
      <link>https://acctress.uk/posts/nature-of-notation/</link>
      <pubDate>Sun, 05 Apr 2026 23:11:51 +0100</pubDate>
      <guid>https://acctress.uk/posts/nature-of-notation/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Whilst designing my functional programming language Lam, I wondered about applications - how can I annotate this application in such a weird way but it still works as intended?&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;If you don&amp;rsquo;t know anything about what I just said, just know an application is just a function call e.g. &lt;code&gt;(+ 1 2) =&amp;gt; 3&lt;/code&gt;.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;This was a good thought experiment for me, because I ended up accidentally creating a positional notation system for numbers based on their relationships in the natural number line. That was a mouthful.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Packrat Parser</title>
      <link>https://acctress.uk/posts/packrat-parser/</link>
      <pubDate>Sun, 05 Apr 2026 00:47:04 +0100</pubDate>
      <guid>https://acctress.uk/posts/packrat-parser/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;I was tweaking my functional language&amp;rsquo;s parser one evening, and I became frustrated with the messiness of my code. It wasn&amp;rsquo;t something I intended, but a natural occurrence which happens from writing parsers like this, I really couldn&amp;rsquo;t do much to fix it without sacrificing hours into rewriting it.&lt;/p&gt;
&lt;p&gt;The most annoying issue I was facing was the constant consumption of ignored tokens such as parenthesis, I would call &amp;ldquo;consume&amp;rdquo; every single line which added onto the pile of mess the parser created already - it distracted me from reading the grammar flow of the parse function. And just like any other programmer, I decided to fix this; and i didn&amp;rsquo;t go the easy route I spent a weekend learning about different parsing algorithms, ones I&amp;rsquo;ve never heard of before, that&amp;rsquo;s when I came across Earley parsing - an algorithm for context free grammars.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
