2022-07-30 18:46:56 Whoops - crc I think I may have made a careless mistake in the `mem:*` words 2022-07-30 18:47:46 I think I mislabeled the msw / lsw and as a result, calculating memory offsets is very clunky. 2022-07-30 18:52:10 https://gist.github.com/RickCarlino/da70a5377683ea9133a0d7d3ed94cfe5 2022-07-30 18:52:36 There is an example of the problem. I would like to fix it before the next major release so that people don't have to deal with the issue. 2022-07-30 18:54:31 I’m still behind on finishing adding documentation on some of the words added, so holding the release until after you make any desired changes won’t be a problem. 2022-07-30 18:54:49 OK Great, thanks! 2022-07-30 18:55:05 Please disregard that last DM- looks like Matrix is working properly. Have not used it in > ` year 2022-07-30 18:55:09 s/`/1/ 2022-07-30 18:55:17 *1 2022-07-30 18:55:45 (I’m also hoping to finish the ilo-in-retroforth/nga soon, so would like to get that added too) 2022-07-30 18:59:23 Oh I am not sure I was tracking that one (did not read your post yet- no gopher client on this device). Are you going to be adding the block editor and whatnot to Retro? 2022-07-30 19:03:36 There’s an initial implementation of block support (currently built over the file: words) in the repository, and a port of the block editor in the examples. 2022-07-30 19:05:53 I’m planning to have an implementation of the vm written to run on retro/nga, to allow running the smaller system within the larger one (mainly for debugging purposes, but it might find some other uses) 2022-07-30 19:07:47 http://sprunge.us/NykwPm is a copy of the retro/ilo filesystem notes accessible via http 2022-07-30 19:08:01 Ah, interesting. I still need to give Ilo a deeper look. 2022-07-30 19:12:21 It’s proving to be a pretty nice little thing with much lower resource requirements than nga. I’ve run it on emulated 4-5MHz 8088/8086 systems, and while slow, it’s manageable for small programs. 2022-07-30 19:12:24 For a DOS system, it needs 384K RAM to run; that’ll drop somewhat as the image gets closer to being finished and after I implement bank swapping to storage. 2022-07-30 19:14:35 (Retro/nga, on the same emulated system is painfully slow and doesn’t have anywhere near enough free memory to be useful) 2022-07-30 19:59:51 That's amazing! What do you typically use for your emulator? I might try putting it on a floppy and running it on my 386. 2022-07-30 20:18:13 crc: Just sent you a PR to clean up the `mem:*` API. https://github.com/crcx/retroforth/pull/1/files 2022-07-30 20:18:56 I realize you use sr.ht / fossil, so no need to actually use GH if it complicates things, I figured it makes diffing easier at the very least. 2022-07-30 20:35:55 GitHub PR’s are fine for review, I’ll manually apply it to the fossil master shortly 2022-07-30 20:47:16 The git mirrors should be updated shortly with your changes 2022-07-30 20:47:34 Great, thanks! 2022-07-30 20:51:15 Is there a way to show `%n` numbers in `s:format` as unsigned numbers? 2022-07-30 21:02:26 Not at present 2022-07-30 21:04:35 I’ll look into adding this as part of the unsigned support (I’ve not done much with unsigned values, so functionality around them is pretty much minimal and not well tested so far) 2022-07-30 21:05:30 Ah, OK. I was building a memory inspector to debug the `mem:` issues and noticed that when I called `s:format` with a malloc memory address (via `s:format), sometimes the sign would creep in. 2022-07-30 21:06:04 Eg: `memory1 '%n%n s:format` would show `456-789`. 2022-07-30 21:25:20 Can anyone tell if I introduced cell alignment issues, or am I just having cell alignment issues in my code? https://gist.github.com/RickCarlino/3770763398c7262e1eeec8e53731a4d9 2022-07-30 21:25:34 I am curious to see how this code would behave on a 64-bit build. 2022-07-30 21:32:23 Oh, I think I get it actually. It's just a cell alignment issue in my code. Sorry- I don't manage my own memory often!