Forum comments in chronological order

Disclaimer: I am not responsible for what people (other than myself) write in the forums. Please report any abuse, such as insults, slander, spam and illegal material, and I will take appropriate actions. Don't feed the trolls.

Jag tar inget ansvar för det som skrivs i forumet, förutom mina egna inlägg. Vänligen rapportera alla inlägg som bryter mot reglerna, så ska jag se vad jag kan göra. Som regelbrott räknas till exempel förolämpningar, förtal, spam och olagligt material. Mata inte trålarna.

Jan 2020

The Å-machine

Anonymous
Mon 6-Jan-2020 10:25
Some more things I discovered in the specification 0.3:

Important differences between the specification and the reference implementation:
- STORE_BYTE: "ram[arg1]" should be "ram[field_addr(arg2 / 2, deref(arg1))]" (2x)
- GET_KEY: should start with "if(SPC == auto || SPC == pendingspace) output_space()" (similar to GET_INPUT)

Minor things in the specification:
- MAKE_PAIR, AUX_PUSH_VAL, AUX_POP_VAL: "local variable addr <- TOP", "v <- 0xe000 + count", "v <- pop_serialized()", and "v <- empty list" should use "=" instead of "<-"
- PUSH_ENV: arguments are given as "BYTE/0" in the index but "BYTE" in the detailed description
- def unlink: useless "return" at the end

Suggestions:
- output_value() is another function which should probably be explicitly defined in the specification (e.g. the non-obvious $ syntax for references is never mentioned in the specification)
- The definition of the "SPC" register suggests that only the order of the enum values matters, not their actual values. While this is true during execution, save files store all the registers, so using anything but the values 0-5 would make saves non-portable. It might therefore be better to assign fixed numbers to the enum values in the specification.
lft
Linus Åkesson
Tue 7-Jan-2020 18:19
Thank you!

Autosokoban

Anonymous
Mon 13-Jan-2020 04:03
Any possibility for a source code?

Craverly Heights in Dialog

Anonymous
Tue 14-Jan-2020 00:06
This was very instructive. —Thore

GCR decoding on the fly

Anonymous
Wed 15-Jan-2020 10:54
"For every four bits of data (also known as a nybble), five bits are written to the disk surface, chosen from a table. Let's refer to them as a quintuple."

Or a Quibble.

The Å-machine

Ivoah
Wed 15-Jan-2020 21:19
Are there any plans to create a C implementation? I would love to get Å-machine games running on devices such as the TI Nspire, which already has frotz ported to it.

The Chipophone

Anonymous
Mon 20-Jan-2020 16:57
Linus, you're officially my new hero

Watch Room

Anonymous
Tue 21-Jan-2020 06:38
Solid "contribution"! Did you do the corresponding visuals as well? Would love to know more about how you did it.
Anonymous
Tue 21-Jan-2020 06:39
Would love to know more about how you did it.

Nvm, just found the page.

Reverberations

Anonymous
Thu 23-Jan-2020 18:35
Can't wait to see this performed live!

I heard Bach in Venice Italy in a small church using their church organ. Context really matters and was an awesome auditory and body experience experience from the reverberations.

The Å-machine

lft
Linus Åkesson
Fri 24-Jan-2020 09:09

Ivoah wrote:

Are there any plans to create a C implementation?

Yes, I certainly intend to do that at some point. A platform-independent engine, calling out to an I/O layer that in turn could be implemented using the Glk library, for instance.

But I have some improvements to the Å-machine in mind, and I would prefer to get those in place first, while there are still only two official interpreters to maintain.

Watch Room

Anonymous
Fri 24-Jan-2020 22:56
Hi, kudos for your blog and for sharing your passion !
any chance you could share that awesome tune in .sid format ?
Anonymous
Fri 24-Jan-2020 23:12
https://www.linusakesson.net/scene/a-mind-is-born/index.php