00:00:00 --- log: started forth/20.11.06 00:05:04 larsb: which cpu? 00:12:16 From the information you provided the hardware simply can not be _interactive_. That obviously does not mean that some forth dialect can not be ""cross-compiled"". 00:18:00 --- join: mtsd joined #forth 00:22:53 inode: It's Marvin Minsky's TT2500, a Logo computer from the MIT AI lab. 00:23:25 --- quit: imode (Quit: WeeChat 2.9) 00:24:17 DKordic: One option would be to define a Forth VM and have the native code interpret that. 00:25:26 But I'm considering subroutine threading. There would be no >R R> accessing the real return stack. For a toy Forth that might be ok. 00:28:47 Is this an enterprise Forth? 00:29:15 Toy languages are the best anyway 00:31:04 Yeah I agree with implement some kind of VM 00:32:00 If you can edit machine's text live then that's a possibility as well, but I assume that's impossible? 00:32:07 Nothing enterprise about it. Just a hobby thig. 00:32:33 veltas, not it's possible. The code space is in a separate 16x4K memory, but it's run time writable. 00:33:13 So indirect jumps *could* be implemented by writing a runtime generated instruction to, say, location 0 and jump there. 00:33:42 But this sounds like a loss for a NEXT primitive. 00:52:30 Yep 00:59:52 --- join: imode joined #forth 01:00:42 --- quit: Vedran (Quit: The Lounge - https://thelounge.github.io) 01:01:59 --- join: Vedran joined #forth 01:10:26 --- quit: jedb (Ping timeout: 240 seconds) 01:10:51 --- quit: Vedran (Quit: The Lounge - https://thelounge.github.io) 01:11:01 --- join: Labu joined #forth 01:12:40 --- join: jedb joined #forth 01:12:41 Some tweets about the background for this Forth: 01:12:44 https://twitter.com/larsbrinkhoff/status/1309438464149127168 01:13:40 --- join: Vedran joined #forth 01:31:49 --- join: marksmith joined #forth 01:35:05 --- quit: dave0 (Read error: Connection reset by peer) 01:40:19 --- join: dave0 joined #forth 02:04:58 --- quit: imode (Ping timeout: 256 seconds) 02:13:46 --- quit: mtsd (Ping timeout: 240 seconds) 03:24:29 larsb: do you have any documentation about that cpu? i saw your post on comp.lang.logo about it being a custom TTL design (sounds interesting) and the only hints about its instruction set i've found are in your MinskyForth/assembler.lisp file 03:27:44 The problem with this computer is that everything is on MIT backup tapes, and files can't be released without a lengthy process. 03:28:25 I have written a simulator which is online in my GitHub simh fork. 03:28:59 Presumably someone could clean-room document the hardware from that. 03:29:40 Side note: people still read comp.lang.logo? I thought it was dead. 03:31:09 This should give an idea what the hardware looks like: 03:31:10 https://github.com/larsbrinkhoff/simh/tree/lars/tt2500/tt2500 03:31:54 I have taken the commenting style from the Able VM. ;-) 03:35:53 I heard from someone outside MIT who says he has schematics, so maybe they can be scanned. 03:41:44 --- join: TCZ joined #forth 04:10:40 --- join: Gromboli joined #forth 05:21:03 --- quit: TCZ (Quit: Leaving) 05:46:35 --- join: Zarutian_HTC joined #forth 06:09:41 --- quit: Zarutian_HTC (Ping timeout: 246 seconds) 06:23:43 --- join: Zarutian_HTC joined #forth 07:31:28 Yay Michigan! 07:31:38 Sorry, wrong channel. 07:31:40 --- part: larsb left #forth 07:32:35 lol 07:34:07 --- join: TCZ joined #forth 07:35:54 --- quit: dave0 (Quit: dave's not here) 08:10:31 --- quit: TCZ (Quit: Leaving) 08:14:31 --- join: TCZ joined #forth 08:21:11 --- quit: Zarutian_HTC (Read error: Connection reset by peer) 08:25:37 --- quit: TCZ (Quit: Leaving) 08:28:56 --- join: Zarutian_HTC joined #forth 08:33:29 --- quit: iyzsong (Ping timeout: 260 seconds) 09:02:32 --- quit: jsoft (Ping timeout: 272 seconds) 10:03:26 --- join: iyzsong joined #forth 10:34:44 --- quit: gravicappa (Ping timeout: 256 seconds) 10:35:52 --- join: gravicappa joined #forth 10:38:09 --- join: imode joined #forth 10:50:24 --- join: WickedShell joined #forth 11:03:09 --- quit: Vedran (Ping timeout: 260 seconds) 11:04:20 --- join: Vedran joined #forth 11:09:50 --- quit: Vedran (Ping timeout: 260 seconds) 11:10:32 --- join: Vedran joined #forth 11:11:44 --- quit: marksmith (Ping timeout: 272 seconds) 11:37:52 --- quit: Vedran (Read error: Connection reset by peer) 12:29:12 --- quit: gravicappa (Ping timeout: 258 seconds) 12:35:39 --- join: proteusguy joined #forth 13:03:56 --- join: Vedran joined #forth 13:12:47 --- quit: proteusguy (Remote host closed the connection) 13:56:50 --- quit: MrMobius (Ping timeout: 268 seconds) 14:07:39 --- join: TCZ joined #forth 14:10:01 --- join: MrMobius joined #forth 14:10:14 --- quit: MrMobius (Remote host closed the connection) 14:11:19 --- join: MrMobius joined #forth 14:25:00 --- quit: Zarutian_HTC (Remote host closed the connection) 14:26:39 --- join: Zarutian_HTC joined #forth 14:33:29 --- quit: Zarutian_HTC (Remote host closed the connection) 14:36:26 --- join: Zarutian_HTC joined #forth 14:52:23 --- quit: TCZ (Quit: Leaving) 14:55:44 --- quit: Zarutian_HTC (Ping timeout: 265 seconds) 14:58:06 --- join: jsoft joined #forth 14:59:33 --- join: Zarutian_HTC joined #forth 15:00:44 --- quit: Zarutian_HTC (Read error: Connection reset by peer) 15:00:54 --- join: Zarutian_HTC joined #forth 15:08:53 --- quit: Zarutian_HTC (Remote host closed the connection) 15:21:51 --- join: TCZ joined #forth 15:56:26 --- quit: TCZ (Quit: Leaving) 16:42:35 --- join: TCZ joined #forth 17:18:45 --- quit: WickedShell (Remote host closed the connection) 17:32:48 --- quit: TCZ (Quit: Leaving) 18:36:25 --- quit: _whitelogger (Remote host closed the connection) 18:39:23 --- join: _whitelogger joined #forth 18:45:01 --- join: boru` joined #forth 18:45:03 --- quit: boru (Disconnected by services) 18:45:06 --- nick: boru` -> boru 19:11:19 --- join: proteusguy joined #forth 19:17:57 --- quit: proteusguy (Remote host closed the connection) 19:25:12 --- quit: Gromboli (Read error: Connection reset by peer) 19:42:26 --- join: dave0 joined #forth 20:36:12 --- quit: sts-q (Ping timeout: 256 seconds) 20:39:32 --- quit: dave0 (Quit: dave's not here) 20:41:14 --- join: sts-q joined #forth 20:42:10 --- join: gravicappa joined #forth 21:23:45 --- join: lispmacs` joined #forth 21:25:33 hi, I'm working with Arduino-FVM (a Forth VM for Arduino). I am experimenting with with changing AVR registers (GPIO, etc.) with writes to register memory addresses 21:26:02 using @ and ! keywords to read and write to memory 21:26:35 however, Arduino-FVM has a cell size of 2, whereas the registers of interest are only one byte 21:27:47 was just wondering if Forth has a built in way to just write to a single byte of memory, or if I have to write a whole cell to memory 21:28:22 --- quit: lispmacs` (Remote host closed the connection) 21:28:34 sorry, I'm back 21:36:33 looks like there are the c@ and c! versions. I think that is what I needed 22:24:58 --- quit: dddddd (Ping timeout: 272 seconds) 22:26:17 --- join: dddddd joined #forth 22:44:16 --- quit: Labu (Ping timeout: 256 seconds) 22:44:37 --- join: Labu joined #forth 22:46:46 --- quit: gravicappa (Ping timeout: 240 seconds) 22:47:13 --- join: gravicappa joined #forth 22:53:59 --- quit: Labu (Ping timeout: 264 seconds) 22:55:34 lispmacs: yep! 22:55:49 ah I was wondering if anyone used AVR here, heh 23:04:37 --- quit: lispmacs (Ping timeout: 260 seconds) 23:13:26 --- quit: jsoft (Ping timeout: 246 seconds) 23:59:59 --- log: ended forth/20.11.06