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.
- Jun 2007
- Aug 2007
- Oct 2007
- Nov 2007
- Dec 2007
- Jan 2008
- Feb 2008
- Mar 2008
- Apr 2008
- May 2008
- Jun 2008
- Jul 2008
- Aug 2008
- Sep 2008
- Oct 2008
- Nov 2008
- Dec 2008
- Jan 2009
- Feb 2009
- Mar 2009
- Apr 2009
- May 2009
- Jun 2009
- Jul 2009
- Aug 2009
- Sep 2009
- Oct 2009
- Nov 2009
- Dec 2009
- Jan 2010
- Feb 2010
- Mar 2010
- Apr 2010
- May 2010
- Jun 2010
- Jul 2010
- Aug 2010
- Sep 2010
- Oct 2010
- Nov 2010
- Dec 2010
- Jan 2011
- Feb 2011
- Mar 2011
- Apr 2011
- May 2011
- Jun 2011
- Jul 2011
- Aug 2011
- Sep 2011
- Oct 2011
- Nov 2011
- Dec 2011
- Jan 2012
- Feb 2012
- Mar 2012
- Apr 2012
- May 2012
- Jun 2012
- Jul 2012
- Aug 2012
- Sep 2012
- Oct 2012
- Nov 2012
- Dec 2012
- Jan 2013
- Feb 2013
- Mar 2013
- Apr 2013
- May 2013
- Jun 2013
- Jul 2013
- Aug 2013
- Sep 2013
- Oct 2013
- Nov 2013
- Dec 2013
- Jan 2014
- Feb 2014
- Mar 2014
- Apr 2014
- May 2014
- Jun 2014
- Jul 2014
- Aug 2014
- Sep 2014
- Oct 2014
- Nov 2014
- Dec 2014
- Jan 2015
- Feb 2015
- Mar 2015
- Apr 2015
- May 2015
- Jun 2015
- Jul 2015
- Aug 2015
- Sep 2015
- Oct 2015
- Nov 2015
- Dec 2015
- Jan 2016
- Feb 2016
- Mar 2016
- Apr 2016
- May 2016
- Jun 2016
- Jul 2016
- Aug 2016
- Sep 2016
- Oct 2016
- Nov 2016
- Dec 2016
- Jan 2017
- Feb 2017
- Mar 2017
- Apr 2017
- May 2017
- Jun 2017
- Jul 2017
- Aug 2017
- Sep 2017
- Oct 2017
- Nov 2017
- Dec 2017
- Jan 2018
- Feb 2018
- Mar 2018
- Apr 2018
- May 2018
- Jun 2018
- Jul 2018
- Aug 2018
- Sep 2018
- Oct 2018
- Nov 2018
- Dec 2018
- Jan 2019
- Feb 2019
- Mar 2019
- Apr 2019
- May 2019
- Jun 2019
- Jul 2019
- Aug 2019
- Sep 2019
- Oct 2019
- Nov 2019
- Dec 2019
- Jan 2020
- Feb 2020
- Mar 2020
- Apr 2020
- May 2020
- Jun 2020
- Jul 2020
- Aug 2020
- Sep 2020
- Oct 2020
- Nov 2020
- Dec 2020
- Jan 2021
- Feb 2021
- Mar 2021
- Apr 2021
- May 2021
- Jun 2021
- Jul 2021
- Aug 2021
- Sep 2021
- Oct 2021
- Nov 2021
- Dec 2021
- Jan 2022
- Feb 2022
- Mar 2022
- Apr 2022
- May 2022
- Jun 2022
- Jul 2022
- Aug 2022
- Sep 2022
- Oct 2022
- Nov 2022
- Dec 2022
- Jan 2023
- Feb 2023
- Mar 2023
- Apr 2023
- May 2023
- Jun 2023
- Jul 2023
- Aug 2023
- Sep 2023
- Oct 2023
- Nov 2023
- Dec 2023
- Jan 2024
- Feb 2024
- Mar 2024
- Apr 2024
- May 2024
- Jun 2024
- Jul 2024
- Aug 2024
- Sep 2024
- Oct 2024
- Nov 2024
Jan 2020
Anonymous
Mon 6-Jan-2020 09:25
Mon 6-Jan-2020 09: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.
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 17:19
Linus Åkesson
Tue 7-Jan-2020 17:19
Thank you!
Anonymous
Mon 13-Jan-2020 03:03
Mon 13-Jan-2020 03:03
Any possibility for a source code?
Anonymous
Mon 13-Jan-2020 23:06
Mon 13-Jan-2020 23:06
This was very instructive. —Thore
Anonymous
Wed 15-Jan-2020 09:54
Wed 15-Jan-2020 09: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.
Or a Quibble.
Ivoah
Wed 15-Jan-2020 20:19
Wed 15-Jan-2020 20: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.
Anonymous
Mon 20-Jan-2020 15:57
Mon 20-Jan-2020 15:57
Linus, you're officially my new hero
Anonymous
Tue 21-Jan-2020 05:38
Tue 21-Jan-2020 05: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 05:39
Tue 21-Jan-2020 05:39
Would love to know more about how you did it.
Nvm, just found the page.
Anonymous
Thu 23-Jan-2020 17:35
Thu 23-Jan-2020 17: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.
lft
Linus Åkesson
Fri 24-Jan-2020 08:09
Linus Åkesson
Fri 24-Jan-2020 08: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.
Anonymous
Fri 24-Jan-2020 21:56
Fri 24-Jan-2020 21:56
Hi, kudos for your blog and for sharing your passion !
any chance you could share that awesome tune in .sid format ?
any chance you could share that awesome tune in .sid format ?
Anonymous
Fri 24-Jan-2020 22:12
Fri 24-Jan-2020 22:12
https://www.linusakesson.net/scene/a-mind-is-born/index.php
Stein
Mon 27-Jan-2020 13:16
Mon 27-Jan-2020 13:16
Wow! I just came across this. I had the same revelations back when I first got a guitar amplifier and tried running the C64 audio through it with reverb turned to max. I only did about a minute and a half of the Toccata in D minor because I couldn't do justice to the chords with only 3 SID voices. I had to go by ear since I couldn't read sheet music back then and I got some of the faster passages wrong. Although I grew up with Karl Richter's version I came to prefer Peter Hurford later, so my SID interpretation was based on that.
But as usual, you take it to the next level. This is awesome, thank you!
But as usual, you take it to the next level. This is awesome, thank you!
Anonymous
Mon 27-Jan-2020 20:05
Mon 27-Jan-2020 20:05
Awesome! Like the short movie and your contribution fit perfectly and knowing about it make that movie close with a strong-punch!