<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Compiler on TrustLang</title>
		<link>https://trust-lang.net/en/tags/compiler/</link>
		<description>Recent content in Compiler on TrustLang</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Wed, 09 Sep 2026 15:37:53 +0300</lastBuildDate>
		
			<atom:link href="https://trust-lang.net/en/tags/compiler/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Compiler implementation</title>
				<link>https://trust-lang.net/en/blog/implementation/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://trust-lang.net/en/blog/implementation/</guid>
				<description></description>
			</item>
			<item>
				<title>The Achilles&#39; heel of C&#43;&#43; and the future r̶e̶ evolution</title>
				<link>https://trust-lang.net/en/blog/comparison/cpp-evolution/</link>
				<pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate>
				<guid>https://trust-lang.net/en/blog/comparison/cpp-evolution/</guid>
				<description>&lt;p&gt;Recently I published an opinion about a fundamental economic model of software development that does not contribute (and objectively should not contribute) to a mass transition from C/C++ to &amp;ldquo;safe&amp;rdquo; programming languages &lt;a href=&#34;https://trust-lang.net/en/blog/comparison/code-safety-economy/&#34;&gt;The economics of code safety, or why Rust is not needed&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;But to remain honest with the readers, I decided to also publish a counter-argument article describing the other side of the coin, that is, why C++ will still be replaced sooner or later, and at the same time to try to analyze what the new programming language that will inevitably replace C++ will look like.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Reflections on the Turing machine and the causes of errors in programming languages</title>
				<link>https://trust-lang.net/en/blog/theory/turing-machine/</link>
				<pubDate>Sat, 15 Nov 2025 00:00:00 +0000</pubDate>
				<guid>https://trust-lang.net/en/blog/theory/turing-machine/</guid>
				<description>&lt;p&gt;A couple of years ago I wrote the article &lt;a href=&#34;https://trust-lang.net/en/blog/theory/structured-programming/&#34;&gt;Reflections on structured programming&lt;/a&gt;, in which I tried to sort out the misconception that Edsger Dijkstra proved that any algorithm can be built from just three constructs (sequence, selection, loop). Whereas in reality:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;This theorem was proved (with conditions and restrictions) by the Italian scientists &lt;strong&gt;Böhm and Jacopini&lt;/strong&gt;, and Dijkstra merely referred to it.&lt;/li&gt;&#xA;&lt;li&gt;The three mentioned basic algorithmic constructs are &lt;strong&gt;insufficient&lt;/strong&gt; for modern programming (for example, exception handling is required).&lt;/li&gt;&#xA;&lt;li&gt;The famous criticism of the &lt;code&gt;goto&lt;/code&gt; statement by Dijkstra (as well as of the assignment statement, which is always forgotten to mention) was not a strict ban, but merely a &lt;strong&gt;recommendation for improving code style&lt;/strong&gt;, so that programs would be easier to analyze.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;And now the time has come to write about some problems of the Turing machine — the fundamental basis of all information technology.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Nuances of developing a parser for your own programming language</title>
				<link>https://trust-lang.net/en/blog/implementation/parser-nuances/</link>
				<pubDate>Wed, 29 Mar 2023 00:00:00 +0000</pubDate>
				<guid>https://trust-lang.net/en/blog/implementation/parser-nuances/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;https://trust-lang.net/en/blog/langs.jpeg&#34; alt=&#34;Featured image&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Recently I read an article on Habr, &amp;ldquo;My own language, or how I got tired of assembler and C&amp;rdquo;, and my eye involuntarily caught on one paragraph:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;I decided not to bother too much, so I used the parglare library. It is very lightweight and convenient, I recommend it to everyone. To describe the syntax, the parser accepts a string in the corresponding format and uses regular expressions (do not judge regexes, they are omnipotent!).&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
