<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mu/linux, branch hlt</title>
<subtitle>Soul of a tiny new machine. More thorough tests → More comprehensible and rewrite-friendly software → More resilient society.
</subtitle>
<id>https://git.tilde.institute/akkartik/mu/atom?h=hlt</id>
<link rel='self' href='https://git.tilde.institute/akkartik/mu/atom?h=hlt'/>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akkartik/mu/'/>
<updated>2022-01-09T15:50:09Z</updated>
<entry>
<title>obsolete argument</title>
<updated>2022-01-09T15:50:09Z</updated>
<author>
<name>Kartik K. Agaram</name>
<email>vc@akkartik.com</email>
</author>
<published>2022-01-09T15:50:09Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akkartik/mu/commit/?id=9cbaad0811705db52a93abf7cec26deabe164b29'/>
<id>urn:sha1:9cbaad0811705db52a93abf7cec26deabe164b29</id>
<content type='text'>
</content>
</entry>
<entry>
<title>keep 'grapheme-stack'</title>
<updated>2021-11-09T17:29:56Z</updated>
<author>
<name>Kartik Agaram</name>
<email>vc@akkartik.com</email>
</author>
<published>2021-11-09T17:29:56Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akkartik/mu/commit/?id=53d69dd1c5707a1cddd5c2ca6827b9a517659eeb'/>
<id>urn:sha1:53d69dd1c5707a1cddd5c2ca6827b9a517659eeb</id>
<content type='text'>
We want to at least document intent there.
</content>
</entry>
<entry>
<title>rename grapheme to code-point-utf8</title>
<updated>2021-11-09T16:12:11Z</updated>
<author>
<name>Kartik K. Agaram</name>
<email>vc@akkartik.com</email>
</author>
<published>2021-11-09T16:12:11Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akkartik/mu/commit/?id=d253a3182859c7c989449122a60d5f362f19ded0'/>
<id>urn:sha1:d253a3182859c7c989449122a60d5f362f19ded0</id>
<content type='text'>
Longer name, but it doesn't lie. We have no data structure right now for
combining multiple code points. And it makes no sense for the notion of
a grapheme to conflate its Unicode encoding.
</content>
</entry>
<entry>
<title>copy back some error messages from linux/</title>
<updated>2021-11-09T15:30:44Z</updated>
<author>
<name>Kartik K. Agaram</name>
<email>vc@akkartik.com</email>
</author>
<published>2021-11-09T15:30:44Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akkartik/mu/commit/?id=d1808995b2c6b99749237a29e6ac6477d00ff8f9'/>
<id>urn:sha1:d1808995b2c6b99749237a29e6ac6477d00ff8f9</id>
<content type='text'>
</content>
</entry>
<entry>
<title>.</title>
<updated>2021-09-13T11:53:38Z</updated>
<author>
<name>Kartik K. Agaram</name>
<email>vc@akkartik.com</email>
</author>
<published>2021-09-13T11:53:38Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akkartik/mu/commit/?id=77207192ea296f040c77cb41fd3966fecce813bb'/>
<id>urn:sha1:77207192ea296f040c77cb41fd3966fecce813bb</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fix bad terminology: grapheme -&gt; code point</title>
<updated>2021-08-30T05:20:09Z</updated>
<author>
<name>Kartik K. Agaram</name>
<email>vc@akkartik.com</email>
</author>
<published>2021-08-30T05:16:34Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akkartik/mu/commit/?id=6e05a8fa27139ddf75a029ad94d44b48a92785b2'/>
<id>urn:sha1:6e05a8fa27139ddf75a029ad94d44b48a92785b2</id>
<content type='text'>
Unix text-mode terminals transparently support utf-8 these days, and so
I treat utf-8 sequences (which I call graphemes in Mu) as fundamental.

I then blindly carried over this state of affairs to bare-metal Mu,
where it makes no sense. If you don't have a terminal handling
font-rendering for you, fonts are most often indexed by code points and
not utf-8 sequences.
</content>
</entry>
<entry>
<title>compute-offset: literal index</title>
<updated>2021-08-26T05:19:24Z</updated>
<author>
<name>Kartik K. Agaram</name>
<email>vc@akkartik.com</email>
</author>
<published>2021-08-26T05:17:19Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akkartik/mu/commit/?id=c45371b319bb72b331f889f7340834c709e1f8a4'/>
<id>urn:sha1:c45371b319bb72b331f889f7340834c709e1f8a4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>.</title>
<updated>2021-08-26T04:46:22Z</updated>
<author>
<name>Kartik K. Agaram</name>
<email>vc@akkartik.com</email>
</author>
<published>2021-08-26T04:46:22Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akkartik/mu/commit/?id=9b62454975ef7cd0ef21ed8edd113f8209f32c11'/>
<id>urn:sha1:9b62454975ef7cd0ef21ed8edd113f8209f32c11</id>
<content type='text'>
</content>
</entry>
<entry>
<title>another long-overdue bugfix</title>
<updated>2021-08-23T06:06:51Z</updated>
<author>
<name>Kartik K. Agaram</name>
<email>vc@akkartik.com</email>
</author>
<published>2021-08-23T06:06:51Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akkartik/mu/commit/?id=2d2c46da5c8886f369de27a3a2793cf3e2335a16'/>
<id>urn:sha1:2d2c46da5c8886f369de27a3a2793cf3e2335a16</id>
<content type='text'>
If I forgot a 'var', Mu would interpret the ':' in the var declaration
as a named block, and all parsing after would be thrown off.

Perhaps I should use separate characters for defining blocks vs vars.
</content>
</entry>
<entry>
<title>fix a long-standing bug in Mu's translator</title>
<updated>2021-08-23T05:10:02Z</updated>
<author>
<name>Kartik K. Agaram</name>
<email>vc@akkartik.com</email>
</author>
<published>2021-08-23T05:10:02Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akkartik/mu/commit/?id=791a71e27eb7a4c906c4454b6a49643a98662df6'/>
<id>urn:sha1:791a71e27eb7a4c906c4454b6a49643a98662df6</id>
<content type='text'>
While all test pass, this change is disquieting. When I first designed
Mu I deliberately chose to exclude literal strings from most primitive
instructions both for type-checking and to avoid silently passing
through strange constructions. Nobody really needs to add a string to a
number, and am I sure no SubX instruction will cause a memory safety
issue when passed a string literal instead of a number?

But clearly I have no tests encoding this desire. And any string literal
could be replaced by an integer literal containing the exact same value,
so what are we protecting against anyway.

Let me fix the bug for now. If I run into problems I'll come back and do
this right.
</content>
</entry>
</feed>
