From ab4459ea2446ced5b93e84aa779f29d80708f374 Mon Sep 17 00:00:00 2001 From: Melody Horn Date: Sat, 14 Sep 2024 15:44:33 -0600 Subject: 11ty --- _posts/2020-10-19-crowbar-3-this-is-tough.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to '_posts/2020-10-19-crowbar-3-this-is-tough.md') 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 a499bc1..4caa701 100644 --- a/_posts/2020-10-19-crowbar-3-this-is-tough.md +++ b/_posts/2020-10-19-crowbar-3-this-is-tough.md @@ -1,8 +1,11 @@ --- title: "Crowbar: Turns out, language development is hard" +description: > + 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. --- -(Previously in Crowbar: [Defining a good C replacement](/2020/09/28/crowbar-1-defining-a-c-replacement.md), [Simplifying C's type names](/2020/10/13/crowbar-2-simplifying-c-type-names.md)) +(Previously in Crowbar: [Defining a good C replacement](_posts/2020-09-28-crowbar-1-defining-a-c-replacement.md), [Simplifying C's type names](_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