From 4bd4d8dab61993b7d24ee1ca147264ad761dfc68 Mon Sep 17 00:00:00 2001 From: Melody Horn Date: Mon, 19 Oct 2020 23:51:57 -0600 Subject: link to the right thing --- _posts/2020-10-19-crowbar-3-this-is-tough.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2020-10-19-crowbar-3-this-is-tough.md b/_posts/2020-10-19-crowbar-3-this-is-tough.md index 1c8f12c..85dd7bd 100644 --- a/_posts/2020-10-19-crowbar-3-this-is-tough.md +++ b/_posts/2020-10-19-crowbar-3-this-is-tough.md @@ -2,7 +2,7 @@ title: "Crowbar: Turns out, language development is hard" --- -(Previously in Crowbar: [Defining a good C replacement]({% link _posts/2020-09-28-crowbar-1-defining-a-c-replacement.md %}), [Simplifying C's type names]({% link _posts/2020-10-13-crowbar-3-this-is-tough.md %})) +(Previously in Crowbar: [Defining a good C replacement]({% link _posts/2020-09-28-crowbar-1-defining-a-c-replacement.md %}), [Simplifying C's type names]({% link _posts/2020-10-13-crowbar-2-simplifying-c-type-names.md %})) Originally, I hadn't decided whether Crowbar should be designed with an eye towards compiling to C or with an eye towards compiling directly. Compiling to C massively cuts down the scope of Crowbar as a project, but compiling directly gives me more comprehensive control over what all happens. -- cgit v1.2.3