00:00:00 --- log: started forth/19.11.19 00:02:10 --- join: SysDsnEng joined #forth 00:09:10 --- join: mtsd joined #forth 00:39:45 --- nick: jn___ -> jn__ 01:26:23 --- join: xek joined #forth 01:55:51 --- quit: mtsd (Remote host closed the connection) 01:56:14 --- join: mtsd joined #forth 02:26:57 --- join: dave0 joined #forth 02:31:17 --- quit: SysDsnEng (Quit: SysDsnEng) 02:39:33 --- join: iyzsong joined #forth 03:18:33 --- quit: jedb__ (Ping timeout: 276 seconds) 03:33:22 --- join: jedb joined #forth 03:35:20 --- join: jedb_ joined #forth 03:36:51 --- quit: jedb (Read error: Connection reset by peer) 03:46:02 --- join: dzho joined #forth 03:52:01 --- quit: proteusguy (Ping timeout: 240 seconds) 04:00:39 --- quit: dys (Ping timeout: 240 seconds) 04:05:50 --- join: proteusguy joined #forth 04:05:50 --- mode: ChanServ set +v proteusguy 04:10:44 --- quit: dzho (Quit: leaving) 04:10:55 --- join: dzho joined #forth 05:27:58 --- quit: iyzsong (Quit: ZNC 1.7.1 - https://znc.in) 05:30:54 --- join: SysDsnEng joined #forth 05:50:59 --- quit: mtsd (Ping timeout: 240 seconds) 06:02:04 --- join: proteus-guy joined #forth 06:09:12 --- quit: dave0 (Quit: dave's not here) 06:34:56 --- quit: SysDsnEng (Quit: SysDsnEng) 06:49:56 --- quit: inode (Quit: ) 06:53:52 --- join: mtsd joined #forth 06:54:39 --- quit: mtsd (Client Quit) 07:32:45 --- quit: tabemann (Ping timeout: 245 seconds) 08:36:26 --- join: jedb__ joined #forth 08:38:42 --- quit: jedb_ (Read error: Connection reset by peer) 08:44:39 --- join: dddddd joined #forth 09:46:54 --- join: ryke joined #forth 10:07:59 --- quit: proteusguy (Ping timeout: 240 seconds) 10:20:50 --- join: proteusguy joined #forth 10:20:50 --- mode: ChanServ set +v proteusguy 10:25:36 --- quit: proteus-guy (Ping timeout: 276 seconds) 11:46:34 --- join: WickedShell joined #forth 12:22:35 --- quit: gravicappa (Ping timeout: 265 seconds) 12:40:16 --- join: inode joined #forth 12:42:00 --- quit: ryke (Remote host closed the connection) 12:42:17 --- join: ryke joined #forth 13:00:00 --- quit: Keshl (Read error: Connection reset by peer) 13:00:22 --- join: Keshl joined #forth 13:05:45 --- join: dys joined #forth 13:18:01 --- join: dave0 joined #forth 14:45:50 --- quit: rpcope (Ping timeout: 250 seconds) 14:46:37 --- join: rpcope joined #forth 15:27:50 --- join: jedb_ joined #forth 15:30:28 --- quit: jedb__ (Ping timeout: 250 seconds) 15:31:45 --- quit: ryke (Ping timeout: 276 seconds) 16:03:28 --- quit: dys (Ping timeout: 265 seconds) 16:13:10 --- quit: xek (Ping timeout: 245 seconds) 16:17:00 --- quit: X-Scale (Ping timeout: 265 seconds) 16:27:13 --- join: X-Scale joined #forth 17:02:51 --- join: X-Scale` joined #forth 17:02:55 --- quit: X-Scale (Ping timeout: 246 seconds) 17:03:34 --- nick: X-Scale` -> X-Scale 17:04:15 --- quit: dave0 (Quit: dave's not here) 17:09:36 --- join: tabemann joined #forth 17:23:15 hey guys 17:40:01 --- quit: pareidolia (Ping timeout: 240 seconds) 18:00:49 --- quit: tabemann (Ping timeout: 240 seconds) 18:15:07 Sunrise: 06:31:39 18:15:07 Sunset: 19:14:33 18:15:07 Total Daylight Hours: 12:42:54 18:15:07 Solar noon: 12:53:06 18:15:10 hey tab 18:29:30 --- join: pareidolia joined #forth 19:33:07 --- join: tabemann joined #forth 19:34:32 all's quiet in Forth land today ? 19:36:01 hey tp 19:36:24 hey tabemann, whats new ? 19:36:33 trying to figure out what to do 19:37:04 thats always the point that I love and hate at the same time 19:37:25 I can't even figure out a legitimate reason to use tasks 19:37:34 it's unbridled opportunity and unbridled confusion rolled into one 19:37:36 yes there's blinkenlichten 19:37:56 but blinkenlichten can be implemented with timer interrupts in a much simpler fashion 19:38:20 I used to suffer from terrible new project start-itus 19:38:31 and a timer interrupt is much cheaper than PAUSE is 19:40:02 really the only reason I see to use tasks is to do something while the user can still enter and execute code at the prompt 19:40:50 do you mean preemptive multitasking tasks ? 19:40:59 cooperative or preemptive 19:41:20 There is a reason for for a task 19:41:49 I use it so I have a reasonable terminal response while testing code loops 19:42:14 that's what I mean 19:42:46 because Forth is all about interaction, I have tons of register pretty print words in flash so I can examine their contents in real time 19:42:59 as the test program is running 19:43:14 it's a bit like GDB, but far easier to use 19:44:35 I've thought of something I should implement 19:44:40 a SIGINT handler 19:44:56 which stops all the tasks except the main one 19:45:04 and returns control to it 19:45:52 and then have another task which restarts all the tasks that had been stopped before 19:45:55 this is a pic of what I mean (see terminal part) and also includes the rest of my IDE layout https://mecrisp-stellaris-folkdoc.sourceforge.io/modern-forth-development-environment.html?highlight=register 19:47:25 in the pic RCC_AHBENR shows that all the GPIOS have been enabled 19:48:35 I manually add the bitfield legends for the most used registers I create the development package for that MCU 19:49:10 all others just get a default 32 bit legend showing the bitfields which at least is useful with a datasheet 19:52:08 --- join: TheBlueWizard joined #forth 19:54:38 but yeah, I ought to implement a SIGINT handler 19:56:48 I think we have that with Mecrisp-Stellaris but I never use it 19:57:07 ie I can manually stop tasks or start them 19:57:36 But tasks are expensive and so I only run two, the terminal and the project 19:58:03 8kB of ram doesnt go far when it comes to tasks 20:00:18 back 20:00:26 welcome back! 20:00:33 wb 20:00:49 yeah, tasks in hashforth are pretty heavy-weight 20:01:39 even in Mecrisp-Stellaris that take about 800 Bytes each 20:07:06 I tend to allocate a lot of space to my task just to make sure they have enough stack and rstack space 20:07:58 and a good amount of space is automatically allocated for user variables 20:09:04 which will limit you to the same kind of micros that can run micropython or eLUA, namely 256kB Flash and above 20:09:36 --- join: ryke joined #forth 20:09:43 forths written for PC's tend to be Godzillas, resource wise 20:13:26 my Forth can be significantly stripped down w.r.t. resources 20:13:52 part of the reason why my Forth uses so much space is that it's on a 64-bit platform :P 20:16:10 understand 20:16:44 thats why Coetex-M "thumb" exists, it maps all instructions into 16 bit to save space 20:17:08 --- part: TheBlueWizard left #forth 20:17:51 Imagine using 4 bytes to encode a single instruction with 4 bytes 20:18:00 This message brought to you by the 6502 gang 20:18:41 that's also why hashforth can be used with 16-bit tokens 20:21:18 (it actually can be used with 8/16-bit tokens if one so desires) 20:22:03 ryke, ahh, youre that 6502 fanatic! ;-) 20:22:10 I did a brain fart 20:22:24 idk if I would call myself a fanatic 20:22:33 The 6502 is my latest object of interest though 20:23:04 ryke, you own a C64, thats proof of fanaticism enough ;-) 20:23:13 Ok ok fair enough 20:23:16 heheh 20:23:24 That was a gift though if that's worth anything 20:23:32 I have owned a few 6502 systems myself 20:23:48 and Atari made megabucks from them 20:24:05 I still have my heart set on getting a hold of a 6502 trainer 20:24:09 I think they're neat 20:24:28 it's simply outstanding what a single 5602 chip can do 20:24:32 6502 !~ 20:26:03 mind you to do anything complex you need lots of instructions on the 6502 20:26:14 adding 32 bits for instance 20:26:18 or even multiplying 8 bits 20:26:21 ryke, I once owned one of these for a couple of years: http://www.oldcomputers.net/AIM-65-40.html 20:26:46 my family owned an Apple //e (with a 6502 of course) back when 20:27:08 tabemann, entire commercial video games had ONE 6502 which did all the game stuff AND ran a VECTOR SCAN monitor in real time 20:27:22 yep 20:27:49 when the game play got frantic with 2 players, the scan rates would slow, but the game never locked up 20:28:19 tp: that looks really neat. Any idea how much one of those run nowadays? 20:29:33 ryke, mine was second hand, I think I paid anout $150 for it back around 1985, it also had a plastic case that everything fitted in 20:30:09 ryke, but it was painful to develop on, I never did anything with it. God knows what theyre worth today 20:30:43 but a single $0.50 cortex-m is about 100 times faster and more capable, and more fun! 20:31:09 but I'm just not the nostalgic type 20:31:39 I believe that nostalgia isn't all it's cracked up to be 20:33:03 --- join: gravicappa joined #forth 20:38:22 ryke, plus they're OLD now and stuff just doesn't last. The thermal printers would be all rusty and gummed up, the IC sockets loose and intermittent 20:38:49 Some things just can't be resurected because theyre too OLD, things like ME! 20:39:26 I've been thinking about messing with ARM 20:40:21 ryke, thats what the AIM65 looked like in it's case: https://en.wikipedia.org/wiki/AIM-65 20:40:53 ryke, even ARM is annoying like the 6502 is, same issues, but the bits have increased is all ;-) 20:42:29 the 6502 was limited to a 8 bit index register so could only jump 254 locations away, Thumb2 jumps further but is limited to 1024 locations for a jump 20:43:22 but if one wants a full 32 bit range to jump then the Flash usage will be humungous 20:48:07 so nothings perfect, and my criticism of the poor old 6502 has always been unfair, especially as it spawned too many industries to count 21:02:41 --- join: Sweedish joined #forth 21:04:43 --- quit: Sweedish (Client Quit) 21:17:40 ryke, the really sad thing about my AIM-65 was that there was a Forth for it and I had no idea what Forth was back then. Life can be cruel! 21:18:51 I wish I knew about Forth when I had my Apple //e 21:19:47 the only thing that gets me about the AIM-65 is how do you get anything done with a single line of text (even though that sure beats blinkenlichten and toggle switches on a front panel) 21:20:11 If I'd had Forth for that AIM65, I would have had so much fun 21:20:31 tabemann, it also had a thermal printer 21:21:00 the inbuilt debugger could printe register values to the printer, code etc 21:23:01 tabemann, and that one line display was alphanumeric, very impressive 21:23:59 the guy I bought it off had just finished designing a electronic cathodic protection unit using the AIM65 21:24:37 he had moved onto a Cromenco Z80 development system which I later also bought from him when he had finished with it 21:33:23 I must've been spoiled by having a system that could do not only full ASCII but which could also draw graphics 21:34:24 and could have 80x24 (I think) text mode availability 21:39:59 yes 21:40:41 got a mechanism to stop all tasks aside from the main task and the sleep task by hitting ctrl-C - even if a task is not reliquishing the CPU 21:41:06 also got a mechanism by which the user can restore stopped tasks 21:53:06 --- quit: gravicappa (Ping timeout: 250 seconds) 21:56:27 --- join: dys joined #forth 22:06:42 --- quit: dddddd (Remote host closed the connection) 22:16:55 --- join: proteus-guy joined #forth 22:39:49 --- quit: yunfan (Quit: WeeChat 1.9.1) 22:52:50 --- join: gravicappa joined #forth 23:13:33 --- join: yunfan joined #forth 23:15:18 --- quit: yunfan (Client Quit) 23:21:51 --- quit: proteus-guy (Ping timeout: 265 seconds) 23:25:52 --- join: yunfan joined #forth 23:26:04 --- quit: yunfan (Client Quit) 23:26:19 --- join: yunfan joined #forth 23:35:36 --- quit: yunfan (Quit: WeeChat 2.3) 23:35:52 --- join: yunfan joined #forth 23:55:47 --- quit: C-Keen (Quit: WeeChat 2.6) 23:59:59 --- log: ended forth/19.11.19