You were being more serious than I thought then? Hah! Though it's a fairly variant language, presumably for the obvious and completely justified reasons, if so.
I seem to have inherited some incomplete ZZT emulation code from my predecessor that converts the program text into 32-bit instruction words first so it can run rather fast. I would be tempted to complete this if there weren't so many other things in the way. Hmm. I think he lost his motivation when someone else started posting facts based on disassembling the ZZT executable, which completely ruined the charm of it.
(Append: and yes, it supports #zap and #restore, including remote, even though the original text is mostly gone—they're implementable by search-and-replace on 32-bit arrays as a result, and on save I think the original text is reconstructed with an offset table (I don't remember whether that bit was fully implemented).)
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
Date: 2013-01-13 07:33 pm (UTC)I seem to have inherited some incomplete ZZT emulation code from my predecessor that converts the program text into 32-bit instruction words first so it can run rather fast. I would be tempted to complete this if there weren't so many other things in the way. Hmm. I think he lost his motivation when someone else started posting facts based on disassembling the ZZT executable, which completely ruined the charm of it.
(Append: and yes, it supports #zap and #restore, including remote, even though the original text is mostly gone—they're implementable by search-and-replace on 32-bit arrays as a result, and on save I think the original text is reconstructed with an offset table (I don't remember whether that bit was fully implemented).)