00:00:00 --- log: started forth/20.12.28 00:04:02 --- join: hosewiejacke joined #forth 01:55:34 --- quit: proteus-guy (Ping timeout: 260 seconds) 02:07:59 --- join: proteus-guy joined #forth 02:21:32 --- quit: jedb_ (Ping timeout: 246 seconds) 02:35:37 Don't want to sound stupid but I'd be using the return stack rather than registers since I'd have to save things anyway on most implementations 02:36:11 Maybe there should be words like R1@ R2@ R3@ R4@ etc to get what's after R@ 02:37:53 Could even *name* those temporarily within the wo-... oh right that's just locals whoops 02:39:00 --- part: hosewiejacke left #forth 02:40:33 Has there been any effort to standardise multi-task forths? 02:41:01 i.e. with suspend/wait/user or whatever they use 02:41:31 It feels like that should be a word set in the standard 02:43:04 --- join: jedb joined #forth 03:01:01 veltas: Not sure, do you mean something like this ? 03:01:01 http://www.greenarraychips.com/home/documents/greg/DB005-120825-PF-REF.pdf 03:01:01 Chapter 4.0 MULTITASKING 03:10:35 --- join: [1]MrMobius joined #forth 03:11:14 --- quit: MrMobius (Ping timeout: 246 seconds) 03:11:15 --- nick: [1]MrMobius -> MrMobius 03:11:27 Yes 03:15:33 I I' J are documented as getting the first, second, and third things on the return stack in starting forth 03:16:15 Makes sense, unfortunately not standard 03:18:38 --- quit: jedb (Ping timeout: 240 seconds) 04:01:30 --- join: xek joined #forth 04:01:38 --- quit: xek (Remote host closed the connection) 04:09:16 --- join: xek joined #forth 04:10:05 --- quit: xek (Client Quit) 04:16:05 --- join: Gromboli joined #forth 04:53:12 --- join: jedb joined #forth 05:05:45 veltas: haha, that's just locals indeed 05:49:09 --- join: xek joined #forth 05:54:11 --- quit: xek (Remote host closed the connection) 05:56:30 veltas, concurrency is definitely not part of any forth standard. I can't imagine one model ever being something forthers would adopt in general. It took C++ 30+ years to define a standard concurrency model and they still ended up with two. 05:56:31 --- join: xek joined #forth 05:57:54 --- quit: xek (Remote host closed the connection) 06:03:58 --- quit: proteus-guy (Ping timeout: 240 seconds) 06:16:28 --- join: proteus-guy joined #forth 07:38:28 hi, I was just wondering if there had been any progress anywhere towards an inexpensive GA144 development board 07:38:33 https://hackaday.io/project/163652-ga144-evaluation-board 08:33:58 I'm not aware of one. Would enjoy playing with such a thing as well. 08:43:28 lispmacs, have you seen this? https://schmartboard.com/schmartboard-ez-qfn-88-pins-0-4mm-pitch-2-x-2-grid-bundled-with-a-greenarrays-ga144-ic-202-0048-02/ 08:52:35 MrMobius, my understanding is that there's still an issue getting hold of the ga144 chips themselves. Hopefully that's no longer the case. 09:01:36 oh hmm 09:01:50 looks like you get the chip too if yoy buy that board 09:23:36 --- join: WickedShell joined #forth 09:32:50 in the forth day update this year it sounded like they still dont have any customers :( 09:33:30 --- quit: gravicappa (Ping timeout: 256 seconds) 09:34:18 --- join: gravicappa joined #forth 09:35:10 Always a danger when you create something that solves problems the way you envisage them, there might be nobody else who thinks the same way 09:35:18 Definitely the case with people like Chuck Moore 09:36:22 If I get a chance I will propagandise the board at work to a design engineer 09:38:48 I have been reading comp.lang.arguing-with-hugh-aguilar 09:40:05 someone called it "a problem looking for a solution" 09:40:31 you have to admit there isnt much of anything where you need 144 cores working in parallel 09:41:31 especially with tiny memories that all have to be individually programmed. I think that's the main thing that kills it, not only lack of a C compiler 09:44:48 woops, make that a solution looking for a problem... 09:54:56 --- join: xek joined #forth 09:55:01 --- quit: xek (Client Quit) 09:59:24 --- join: lispmacs[work] joined #forth 10:11:28 --- quit: Vedran (Ping timeout: 256 seconds) 10:12:23 --- join: Vedran joined #forth 10:38:43 --- quit: cantstanya (Write error: Broken pipe) 10:41:29 veltas: clf is as quiet as other newsgroups once the killfile is properly seeded 10:42:19 --- join: cantstanya joined #forth 11:13:01 "Always a danger when you create something that solves problems..." https://medium.com/swlh/good-technology-bad-investment-7e0d6bfa08dc 11:30:58 --- quit: birdwing (Ping timeout: 240 seconds) 12:02:23 --- quit: gravicappa (Ping timeout: 264 seconds) 12:58:36 wordlists... 15:04:52 --- join: birdwing joined #forth 16:23:47 --- join: dave0 joined #forth 16:43:59 --- join: gravicappa joined #forth 17:02:18 --- quit: gravicappa (Ping timeout: 240 seconds) 17:20:08 Huh, Mostek made a version of their 68200 microcontroller with a FORTH kernel ROM. 17:20:30 Similar to Rockwell's R65F11, but 68000-based instead of 6502 17:31:02 --- join: Rakko joined #forth 18:12:05 --- quit: cantstanya (Ping timeout: 240 seconds) 18:16:20 --- join: cantstanya joined #forth 18:16:46 TangentDelta, neat. do you have a link? 18:16:57 I can only find references to it 18:17:04 whats it called? 18:17:31 https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.467.5001&rep=rep1&type=pdf 18:17:35 F68K 18:17:40 thanks! 18:33:20 --- quit: birdwing (Ping timeout: 260 seconds) 18:46:42 --- join: boru` joined #forth 18:46:44 --- quit: boru (Disconnected by services) 18:46:47 --- nick: boru` -> boru 19:10:46 --- quit: dave0 (Quit: dave's not here) 20:06:51 --- quit: Gromboli (Quit: Leaving) 20:10:21 --- quit: WickedShell (Remote host closed the connection) 20:23:27 --- quit: sts-q (Ping timeout: 240 seconds) 20:38:46 --- join: sts-q joined #forth 21:28:39 --- join: gravicappa joined #forth 23:24:14 --- quit: Vedran (Ping timeout: 256 seconds) 23:42:29 --- join: birdwing joined #forth 23:52:03 --- quit: Rakko (Quit: Leaving) 23:59:59 --- log: ended forth/20.12.28