00:00:00 --- log: started forth/20.11.29 00:22:44 --- quit: proteusguy (Ping timeout: 272 seconds) 00:27:15 --- quit: wineroots (Remote host closed the connection) 00:41:16 --- join: wineroots joined #forth 00:52:59 --- join: proteusguy joined #forth 01:26:24 siraben: Car controller software uses these standards and techniques because they get sued and regulated more. But e.g. military only needs cert if they want to be able to fly through residential areas &c. rather than 'delivering' their aircraft near the field of battle. 01:27:29 And it's worth realising that using even the most sophisticated provers &c. doesn't guarantee the software works, you can still have bugs. 01:28:30 So you still need: good programmers first and foremost, a good process, and then last thing you want is all these tools and standards and people tend to use them based on requirements. 05:51:39 --- join: proteus-guy joined #forth 05:51:39 --- quit: proteusguy (Read error: Connection reset by peer) 07:38:10 --- join: Gromboli joined #forth 07:43:47 --- quit: iyzsong (Quit: ZNC 1.7.5 - https://znc.in) 07:44:17 --- join: iyzsong joined #forth 07:49:12 --- join: Zarutian_HTC joined #forth 08:10:56 --- quit: Zarutian_HTC (Ping timeout: 246 seconds) 08:25:08 --- join: Zarutian_HTC joined #forth 09:19:00 --- quit: tabemann (Ping timeout: 264 seconds) 09:43:18 --- quit: gravicappa (Ping timeout: 240 seconds) 09:51:43 --- quit: Zarutian_HTC (Remote host closed the connection) 09:56:38 --- quit: lispmacs (Ping timeout: 240 seconds) 10:24:34 --- join: Zarutian_HTC joined #forth 10:35:40 --- quit: Zarutian_HTC (Remote host closed the connection) 10:51:24 --- quit: _whitelogger (Remote host closed the connection) 10:54:23 --- join: _whitelogger joined #forth 11:20:39 --- join: gravicappa joined #forth 12:17:23 What Forth implementation do you use on a PC (if any?) I've been using gforth for learning, but was wondering if there's anything else that I could check. 12:20:41 --- quit: gravicappa (Ping timeout: 260 seconds) 12:35:03 if you are prepared to consider 16-bit DOS programs, F-PC 12:42:37 --- join: Zarutian_HTC joined #forth 12:47:11 --- quit: dddddd (Quit: dddddd) 12:47:55 neuro_sys: I'm using gforth at the moment, I have tried a couple others, gforth is the least weird one I've seen. I have barely touched the SwiftForth demo and that seems okay 12:48:11 I'm not really sure I understand what the licensing terms of the demo are, or if it's any different from full version 12:48:22 It comes with a really nice manual, and copies of different standards 12:50:23 I think a forth for PC that gets used quite a bit in here is retro because I see crc actually uses it as much as possible, a good benchmark for using it 12:51:12 --- join: dddddd joined #forth 12:52:29 There's also 8th 12:56:32 inode: 16-bit DOS is good/simple, I'll check 12:56:40 Retro forth also seems good 12:57:26 Also for later I'm curious what's used for embedded applications. Maybe they often roll their own Forth. 13:21:13 Mecrisp is used a lot by people who are/were in here 13:21:43 They have a channel on freenode: #mecrisp. There is also #retro 13:22:11 Mecrisp for embedded 16:27:36 --- join: dave0 joined #forth 16:42:21 --- join: tabemann joined #forth 17:12:10 --- quit: Zarutian_HTC (Ping timeout: 256 seconds) 17:28:40 --- join: lispmacs joined #forth 17:38:42 --- join: Zarutian_HTC joined #forth 18:04:50 question: in multi-tasking Forth environment, my understanding is that each thread has it's own data and return stack, which makes sense. But what about `allot'ed memory? don't things get mixed up when certain tasks want to roll back the pointer? 18:20:31 --- join: boru` joined #forth 18:20:33 --- quit: boru (Disconnected by services) 18:20:36 --- nick: boru` -> boru 18:44:52 --- join: proteusguy joined #forth 18:44:52 --- quit: proteus-guy (Read error: Connection reset by peer) 18:46:58 --- quit: Zarutian_HTC (Remote host closed the connection) 18:50:30 --- quit: lispmacs (Quit: need to reboot. See you on the other side...) 18:53:04 --- quit: proteusguy (Read error: Connection reset by peer) 18:53:19 --- join: proteusguy joined #forth 19:05:58 --- quit: proteusguy (Ping timeout: 240 seconds) 19:08:59 --- quit: dave0 (Quit: dave's not here) 20:17:34 --- quit: Gromboli (Read error: Connection reset by peer) 20:26:06 --- join: gravicappa joined #forth 20:42:05 --- quit: cantstanya (Ping timeout: 240 seconds) 20:43:05 --- join: hosewiejacke joined #forth 20:50:38 --- quit: sts-q (Ping timeout: 240 seconds) 20:57:43 --- join: sts-q joined #forth 21:04:45 --- quit: hosewiejacke (Ping timeout: 260 seconds) 21:10:07 --- join: hosewiejacke joined #forth 21:31:38 --- quit: hosewiejacke (Ping timeout: 240 seconds) 21:40:06 --- join: proteusguy joined #forth 22:13:01 --- join: lispmacs joined #forth 22:22:30 --- join: hosewiejacke joined #forth 23:59:59 --- log: ended forth/20.11.29