00:00:00 --- log: started forth/20.05.31 00:11:14 --- join: iyzsong joined #forth 00:58:03 --- quit: iyzsong (Ping timeout: 246 seconds) 01:03:37 --- join: iyzsong joined #forth 01:26:50 --- quit: Zarutian_HTC (Remote host closed the connection) 01:43:03 --- join: Zarutian_HTC joined #forth 01:57:24 --- quit: _whitelogger (Remote host closed the connection) 02:00:27 --- join: _whitelogger joined #forth 02:02:40 --- join: dddddd joined #forth 02:09:24 --- quit: _whitelogger (Remote host closed the connection) 02:12:27 --- join: _whitelogger joined #forth 03:26:43 --- quit: gravicappa (Ping timeout: 265 seconds) 03:31:04 --- quit: rdrop-exit (Ping timeout: 265 seconds) 03:31:26 --- join: rdrop-exit joined #forth 03:42:49 Is forth.org down? 03:43:47 looks like it is 03:45:36 What's a small Forth implementation you are aware for Z80 systems? 03:46:03 --- quit: rdrop-exit (Ping timeout: 265 seconds) 03:46:27 neuro_sys: I've implemented one 03:46:52 https://github.com/siraben/ti84-forth/blob/master/forth.asm 03:46:56 Thanks! 03:47:26 neuro_sys: Here it is not depending on the TI-OS at all, running from boot 03:47:28 https://github.com/siraben/zkeme80 03:47:30 --- join: rdrop-exit joined #forth 03:47:41 That menu you see was written in Forth. 03:48:31 Amazing, I'm checking 03:53:44 neuro_sys: In Forth implementation in zkeme80 has a unit test suite written in Forth too, which allowed me to fix some bugs from the ti84-forth repo. 04:00:16 * siraben should implement a Forth REPL for the calculator at some point 04:03:57 Doesn't ti84-forth have a REPL already? 04:04:32 neuro_sys: Yeah, that works with the TI-OS though. 04:04:32 Ah, seems like you compile your Forth code, and then transfer it ti-84 04:04:50 Right 04:06:41 After I study Forth deeper, I'd like to do the same for Amstrad CPC. 04:07:11 There's one Fig-Forth implementation for it from 80s, but it uses 32kb RAM. 04:07:42 Hmm, 44K even 04:08:13 neuro_sys: Definitely can be smaller. I was very space constrained. 04:32:38 --- quit: rdrop-exit (Quit: Lost terminal) 05:08:33 --- join: gravicappa joined #forth 05:14:15 --- quit: iyzsong (Ping timeout: 246 seconds) 05:14:50 --- join: iyzsong joined #forth 05:36:38 neuro_sys: I'm working on a Z80 forth for the ZX Spectrum right now, I anticipate the smaller build will be around 8K 05:38:08 Forth is a very good fit for 8-bit computers, in my opinion. 05:38:27 https://github.com/veltas/zenv 05:54:25 --- quit: cantstanya (Ping timeout: 240 seconds) 05:58:36 --- join: cantstanya joined #forth 06:06:59 --- quit: iyzsong (Quit: ZNC 1.7.1 - https://znc.in) 06:43:43 has anyone here heard of in the past an isa or pci card with a microcontroller running forth? I've searched for this and it seems there is no longer evidence for what I remember. 06:51:08 --- join: karswell_ joined #forth 07:15:26 --- quit: gravicappa (Ping timeout: 258 seconds) 07:17:06 --- quit: karswell_ (Ping timeout: 246 seconds) 07:20:50 --- join: karswell_ joined #forth 07:30:53 --- join: andrei-n joined #forth 07:32:12 --- nick: karswell_ -> karswell 08:11:52 --- join: X-Scale` joined #forth 08:14:14 --- quit: X-Scale (Ping timeout: 256 seconds) 08:14:14 --- nick: X-Scale` -> X-Scale 08:46:56 --- join: X-Scale` joined #forth 08:48:32 --- quit: X-Scale (Ping timeout: 272 seconds) 08:48:32 --- nick: X-Scale` -> X-Scale 08:53:20 --- join: WickedShell joined #forth 09:25:09 --- quit: WickedShell (Remote host closed the connection) 09:36:58 --- quit: Zarutian_HTC (Remote host closed the connection) 09:38:47 klys: Out of curiosity, what was the card for other than having a microcontroller with forth on it? 09:39:22 veltas: Very nice 09:39:59 I'm still reading Starting/Thinking Forth slowly, but is there a reference implementation that you guys check? 09:40:15 Even though it seems simple enough roll one from just by reading the language spec 10:23:37 --- join: gravicappa joined #forth 10:31:12 --- quit: karswell (Remote host closed the connection) 10:32:36 --- join: karswell joined #forth 10:46:36 --- quit: karswell (Remote host closed the connection) 10:48:04 --- join: karswell joined #forth 10:57:40 neuro_sys: The reference I see advised before writing a Forth is https://www.bradrodriguez.com/papers/moving1.htm 11:21:54 --- join: Zarutian_HTC joined #forth 11:34:06 hey guys 11:38:15 neuro_sys, it's not easy to say what other purpose it had, given the date I remember it from, though it is possible it would be used in some future (at the time) bios development. 11:41:25 ah, what every person does when they learn forth - write a forth implementation 11:42:16 * tabemann did the same, and now is on his third forth implementation 11:44:37 (forth has probably the highest implementation to user ratio of any language) 13:11:00 look up scheme and generally lisp ,) 13:31:43 --- quit: gravicappa (Ping timeout: 256 seconds) 13:31:43 --- quit: reepca (Read error: Connection reset by peer) 13:32:15 --- join: reepca joined #forth 13:40:09 --- quit: reepca (Read error: Connection reset by peer) 13:40:22 --- join: reepca joined #forth 14:01:13 --- join: TCZ joined #forth 14:07:26 --- quit: andrei-n (Quit: Leaving) 14:11:43 --- nick: TCZ -> DoomSlayer2020 14:18:53 --- quit: karswell (Read error: Connection reset by peer) 14:19:24 --- join: karswell_ joined #forth 14:23:52 --- quit: kamid (Ping timeout: 260 seconds) 15:09:24 --- quit: lonjil (Ping timeout: 260 seconds) 15:09:33 --- join: lonjil2 joined #forth 15:11:35 --- nick: lonjil2 -> lonjil 15:14:08 --- quit: DoomSlayer2020 (Quit: Leaving) 15:26:15 --- quit: tabemann (Read error: Connection reset by peer) 15:32:50 --- join: tabemann joined #forth 15:40:40 hey guys 16:13:43 --- join: dave0 joined #forth 16:29:40 --- quit: kori (Read error: Connection reset by peer) 16:36:47 hery tabemann 16:39:06 tabemann, what does "*** exit status: 0 ***" signify with Zeptoforth ? 16:41:09 tp: nothing 16:41:18 oh good 16:41:19 that is an error from another program 16:41:30 oh 16:41:53 i get it when uploading source to Zeptoforth 16:42:01 using picocom 16:42:18 that's because it cannot handle zeptoforth rebooting 16:42:34 when loading code zeptoforth frequently reboots 16:43:55 I had to modify codeload3.py so it would tolerate this 16:44:20 (if you're not using e4thcom I'd recommend codeload3.py) 16:47:06 --- join: TCZ joined #forth 16:47:31 oh ok 16:47:49 hey I have a code list for you re assembly :) 16:48:37 tabemann, see http://dpaste.com/3KJRNDK 16:48:53 thats my initial foray into the gas dissasembly 16:49:19 next stage is to actually feed it into GAS 16:59:03 --- join: WickedShell joined #forth 17:48:24 --- quit: _whitelogger (Remote host closed the connection) 17:51:27 --- join: _whitelogger joined #forth 18:07:32 --- quit: Zarutian_HTC (Ping timeout: 256 seconds) 18:08:59 back 18:09:50 tabemann, I use freebsd and e4thcom only runs on Linux 18:10:14 tabemann, but gnu screen does what I want once I have RTS hsndshaking 18:10:28 --- join: boru` joined #forth 18:10:31 --- quit: boru (Disconnected by services) 18:10:31 back 18:10:33 --- nick: boru` -> boru 18:10:36 warning 18:11:07 you need to compile your code for flash before dumping it 18:11:25 because see those MOVW/MOVT instructions? 18:11:26 oh 18:11:45 yes 18:11:56 those are referring to addresses in RAM 18:12:05 thats why I pasted the code, I knew youd have suggestions and warnings 18:12:13 whereas when you feed the code into GAS you'll want actual literals 18:12:31 which you'll get if you compile to flash then see-for-gas 18:12:36 okies I'll try that next 18:13:46 actually 18:13:51 forget about that 18:13:53 I misread the code 18:14:03 those are actually just address literals of IO addresses 18:14:22 because I mentally switched around MOVW and MOVT 18:14:30 heh 18:14:31 you don't need to recompile your code 18:14:40 thats easier 18:17:42 I'm still amazed at how much code is generated for so little code 18:18:22 me too 18:18:44 but i'll finish the whole think off with a hand assembled comparison 18:18:47 thing 18:19:16 but sometimes compact code isnt important when developing 18:20:10 one can be wasteful when developing a concept and lots of resources are available. Its a zillion times easier to write and test Forth than assembly 18:24:05 back 18:24:16 I'm looking over the code, and it seems more reasonable from a second glance 18:24:53 one little tip though 18:24:59 if you are really trying to save space 18:25:08 plus a hll rendered down to assy always seems excessive 18:25:08 use [ %10 2 lshift ] literal 18:25:15 rather than %10 2 lshift 18:26:01 I'm not trying to save space, I'm after easy to read code at this point, but I'll try it later 18:27:11 yeah 18:27:26 thanks for the tip tho 18:27:59 having the gas friedly output makes this a lot easier 18:32:22 --- quit: TCZ (Quit: Leaving) 18:40:14 --- quit: va (Remote host closed the connection) 18:40:44 back 18:44:20 --- join: va joined #forth 19:20:15 --- quit: dave0 (Quit: dave's not here) 19:21:17 --- join: ecraven- joined #forth 19:28:48 --- quit: tangentstorm (*.net *.split) 19:28:49 --- quit: ecraven (*.net *.split) 19:28:54 --- nick: ecraven- -> ecraven 19:32:51 --- quit: siraben (Ping timeout: 260 seconds) 19:33:22 --- quit: jimt[m] (Ping timeout: 256 seconds) 19:35:23 --- join: tangentstorm joined #forth 19:54:56 --- join: Croran joined #forth 20:12:27 --- join: jimt[m] joined #forth 20:16:15 --- join: siraben joined #forth 20:38:25 --- join: dave0 joined #forth 20:49:50 --- join: kamid joined #forth 20:57:59 --- quit: dddddd (Ping timeout: 265 seconds) 21:24:27 --- quit: dave0 (Quit: dave's not here) 21:44:28 --- quit: WickedShell (Remote host closed the connection) 21:58:56 --- quit: karswell_ (Ping timeout: 240 seconds) 22:13:09 --- join: kori joined #forth 22:13:09 --- quit: kori (Changing host) 22:13:09 --- join: kori joined #forth 22:14:32 --- quit: kamid (Ping timeout: 256 seconds) 22:16:35 --- join: kamid joined #forth 22:39:26 --- join: gravicappa joined #forth 23:46:15 --- join: dys joined #forth 23:59:59 --- log: ended forth/20.05.31