00:00:00 --- log: started forth/20.04.03 00:12:31 tabemann, re assert ( f "name" -- ) can you give me an example please ? 00:13:04 rdrop-exit, what do you thing tabemann's assert stack picture indicates ? 00:13:37 --- quit: rdrop-exit (Ping timeout: 240 seconds) 00:13:56 --- join: rdrop-exit joined #forth 00:17:12 tp, not sure 00:17:34 "f" is supposed to be a flag 00:17:53 so I read 00:18:10 yes, but he may be mixing the compile-time and execution time stack pictures into one 00:18:55 i get this 00:18:58 1 "fail" assert unable to parse: "fail" 00:19:37 my averts takes an exception name at compile-time, and takes an arbitrary cell at execution time 00:19:39 assuming that "name" is the assert fail name ? 00:19:51 for example: 00:20:05 this is his comment "\ Assert that a value is true, otherwise raise a specified exception 00:20:06 " 00:20:21 ahh, it needs a specified exception ? 00:21:01 : foo ... 32 u< averts xoverflow ... 00:21:21 you could achieve the same with: 00:21:31 and xoverflow is a exception ? 00:21:36 : foo ... 32 u>= triggers xoverflow ... 00:21:45 yes 00:21:55 thats what Im doing wrong then 00:22:18 but that's how I do it, other forths do it differently 00:22:44 sure 00:22:55 my excetion numbers are just the XTs of the corresponding fallback exception handler 00:23:14 this is different from how ANS does exceptions, they're way is more complicated 00:23:26 these would be software exceptions I assume 00:23:39 Im only familiar with hardware exceptions 00:24:17 yes, Forth exceptions, although nothing prevents you in having a hardware exception trigger a forth exception 00:26:02 except that many hardware exceptions will freeze the chip 00:28:09 well you can only percolate a hardware exception to a Forth exception if there's a way to hook the hardware exception 00:28:22 yeah 00:28:27 makes sense 00:28:59 and if the cpu isnt in halt mode because of the hardware exception 00:29:38 they dont like the PC running wild it seems 00:29:41 that can be dealt with in a tethered Forth via JTAG 00:30:33 naturally! 00:30:40 giving you access to the debug controller/subsystem of the chip from your host Forth's command line 00:30:58 yeah, it's a much better dev system for sure 00:31:08 Id love one for cortex-m 00:31:40 maybe tabemann might get inspired to make one sometime 00:31:49 Maybe the guy who made your Forth will make one eventually 00:32:08 at age 66 I doubt I'll live long enuf to try yours ;-) 00:32:27 no, Ive asked him. He hates cortex-m and thumb1 00:33:06 basically his forst Forth was for the MSP430 and he 'ported' it to cortex-m 00:33:25 I don't usually distribute my Forths, they're always very customized to my idiosyncracies 00:33:32 ahh 00:34:19 I understand, Im the only person using my Forth dev system tho a few are using my svd2forth system 00:35:03 211 have downloaded that diagnostic binary I made (in forth) tho theyre all windows arduino users 00:35:08 cool 00:35:24 but only as it has a simple menu 00:36:12 i did write a blinky for it and thats been dl about 11 times as it has to be uploaded to the chip in their terminal 00:37:51 so we had this massive problem with Chinese fake chips, I wrote the bootable binary diagnostic that interrogates the chip, someone else decapped all the variants and took pics so now everyone pretty much understands what they are dealing with 00:38:10 not bad for a few hobbysists 00:38:19 I read your web page on that, pretty cool 00:38:45 some of the Chinese 'compatibles' arent, and there is no tech sheet anywhere for them 00:39:04 I should include the latest decapped pics 00:39:49 the chips are all different, so not a copy, only 'compatible' which is how they dont get sued I guess ? 00:40:11 I haven't been programming during my quarantine, catching up on other things 00:40:26 pulling hair out ? 00:40:35 screaming ? 00:40:43 running around in circles ? 00:40:54 going batshit crazy ? 00:41:34 so how do you get food in your quarantine ? 00:41:42 Fixing organizing stuff in the condo, spending quality time with my wife, reading, watching videos, video conferencing with my kids 00:42:03 We stocked up a couple weeks before the lockdown 00:42:17 the Internet has sure helped with quarantines 00:42:33 can you venture out to buy food ? 00:43:19 yes with a special form you have to fill out, but I've no need to, well stocked up 00:44:13 what do you then do with the special form ? 00:44:41 you give it to the police if they ask what you're up to 00:44:45 ahh 00:45:43 there are 9 shopping centers within walking distance if ever I need to do a run 00:46:25 my wife has fresh fruits and veggies delivered from the province every week 00:46:25 thats a bit like our 'vehicle check'. if a vehicle is unlicensed you can drive it on the road to the nearest vehicle check business, but you must write a letter to the police explaining that and put in your pocked in case pulled over 00:47:17 my biggest worry is eventually running out of espresso beans and cigarettes 00:47:27 so it's fairly well organised ? What about the peseants in the slum areas ? 00:48:32 i guess it's every man for himself out there ? 00:48:39 it varies, most people stay at home, unless they have a logistics or health related job 00:48:48 sounds like here 00:48:57 lots are running deliveries 00:49:11 thayre saying here that Australia will be locked down until September 00:49:32 --- quit: dys (Ping timeout: 258 seconds) 00:51:13 before the quarantine I started working on a new user interface for my pc forth, go tired of dealing with terminal emulators 00:52:13 basign it on the x11 protocol 00:52:25 * basing 00:53:18 4 windows, 1 for the outer interpreter, 3 others for block viewing and editing 00:55:09 is color involved ? ;-) 00:55:53 for the moment, not much the outer-interpreter window will have a different color scheme from the others 00:56:38 sounds good 00:57:47 I've done what I can as far as my programming abilities can take me and Im fappy with my 'semi tethered' Forth ;-) 00:57:57 -f+h 00:58:36 I made that custom raster font I talked about 01:00:34 all ASCII glyphs, and single charcter cell hex pairs 01:01:08 The only character in block that shows up as a blank on the screen is the ASCII space character 01:01:46 hows it look ? all 70's retro ? ;-) 01:02:10 pretty much 70s, the font is large 16x16 01:02:22 pixels per character 01:03:24 that way I can fit two hex charaters in the same space as a single ASCII character 01:03:47 by making each nibble digit 8x16 01:03:56 which is a great idea 01:05:48 I plan on having quasi-mode that will display the a window completly in hex while you hold it down 01:05:56 * a quasi-mode 01:06:19 very handy 01:06:51 let go and your back to ASCII (except for non-glyph characters which are always shown in the hex font) 01:08:23 hmm, youve got me wondering if VIM has a similar facility now 01:08:33 The font looks ok, I don't do any anti-aliasing though which gives it that retro look 01:09:02 Here's the layout of the letter A 01:09:09 ................ 01:09:10 ......****...... 01:09:10 .....******..... 01:09:10 ....***..***.... 01:09:10 ...***....***... 01:09:11 ..***......***.. 01:09:15 ..***......***.. 01:09:18 ..************.. 01:09:19 ..***......***.. 01:09:21 ..***......***.. 01:09:24 ..***......***.. 01:09:26 ..***......***.. 01:09:29 ................ 01:09:31 ................ 01:09:52 what res is the monitor you view it on ? 01:10:10 while this is the layout of a hex 00 occupying the same 16x16 01:10:30 --- quit: rdrop-exit (Quit: Lost terminal) 01:10:45 a "10" would be more relevant 01:11:26 --- join: rdrop-exit joined #forth 01:11:49 got kicked of irc 01:12:08 --- quit: Zarutian_HTC (Remote host closed the connection) 01:12:18 hahah, flooding ? 01:12:33 ..*****.*****... 01:12:34 ..*...*.*...*... 01:12:34 ..*...*.*...*... 01:12:34 ..*...*.*...*... 01:12:34 ..*...*.*...*... 01:12:34 --- join: dys joined #forth 01:12:34 ..*...*.*...*... 01:12:36 ..*...*.*...*... 01:12:39 ..*...*.*...*... 01:12:42 ..*...*.*...*... 01:12:44 ..*...*.*...*... 01:12:47 ..*****.*****... 01:13:25 great idea, it doesnt alter the line lengths 01:13:37 two hex digits occupy the same space as a single display character 01:14:23 I've been wanting to do something like this for a while, now that I'm experimenting with a x11 port seemed a good time 01:15:25 well you have a few months to work on it now when youre not patrolling the rooftop etc 01:15:51 But my main reason it to have both key press and key release events, that's the deficiency of terminals that bothers me the most 01:16:38 It'll mean a complete rewrite of my UI and block editor to take advantage of it 01:17:34 for sure 01:18:36 I want to convert my block editor's incremental search to a quasi-mode like on the Canon Cat 01:20:02 I'm afk for a bit, thanks for the cat! 01:20:25 ciao, stay healthy 01:20:44 --- join: xek joined #forth 02:06:18 --- join: xek_ joined #forth 02:08:46 --- quit: xek (Ping timeout: 260 seconds) 02:21:25 --- join: jsoft joined #forth 02:28:18 --- join: xek__ joined #forth 02:30:55 --- quit: xek_ (Ping timeout: 256 seconds) 03:13:49 --- join: dddddd joined #forth 03:59:22 --- join: Tiketing joined #forth 04:00:07 --- nick: Tiketing -> webchat9 04:43:24 --- quit: rdrop-exit (Quit: Lost terminal) 05:34:50 --- join: Zarutian_HTC joined #forth 05:50:36 --- quit: Zarutian_HTC (Ping timeout: 256 seconds) 06:26:47 --- quit: mtsd (Quit: Leaving) 06:28:40 --- quit: iyzsong (Quit: ZNC 1.7.1 - https://znc.in) 06:29:53 --- join: Zarutian_HTC joined #forth 06:49:44 how to convert ( addr u ) into a counted string ? 06:54:19 cexpect ( cstr-addr maxlength - - ) Read input into a counted string. ? 06:54:33 thats with Mecrisp-Stellaris 06:55:01 S" ABC" 06:55:01 Ok ( 5512227 3 ) 06:55:11 is there a way to make this a counted string ? 06:55:45 type ? 06:56:14 type will print it out 06:56:43 oh ok, I'm still a noob, much I havent done with Forth 06:56:52 I want to convert it to the same thing which is returned by C" ABC" 07:25:35 --- join: jsoft_ joined #forth 07:26:04 --- quit: jsoft (Quit: Leaving) 07:26:18 --- quit: jsoft_ (Client Quit) 07:26:38 --- join: jsoft joined #forth 08:02:21 --- quit: cheater (Ping timeout: 252 seconds) 08:02:57 --- join: cheater joined #forth 08:03:14 webchat9: You will need to allocate a count bytes!! Therefore it needs to be copyed, including over itself, or in-place? 08:03:43 s/a count/the count/ 08:06:29 Have You looked at the ' ," ' s" and ' c" source code? 08:38:37 --- join: Zarutian_HTC| joined #forth 08:38:37 --- quit: Zarutian_HTC (Read error: Connection reset by peer) 08:41:14 --- quit: jsoft (Ping timeout: 260 seconds) 08:41:41 --- quit: dave0 (Quit: dave's not here) 08:48:19 --- quit: cheater (Ping timeout: 258 seconds) 09:04:45 --- quit: dys (Ping timeout: 256 seconds) 09:19:01 --- quit: remexre (Ping timeout: 268 seconds) 09:21:31 --- join: dys joined #forth 09:22:43 --- join: cheater joined #forth 09:26:57 --- nick: fiddlerwoaroof_ -> fiddlerwoaroof 09:29:37 DKordic: haven't looked, I'll take a look thanks 09:31:46 --- quit: diginet2 (*.net *.split) 09:32:01 --- join: diginet2 joined #forth 09:52:33 --- quit: Zarutian_HTC| (Read error: Connection reset by peer) 10:43:52 --- join: john_cephalopoda joined #forth 10:44:23 Hi 10:55:29 --- join: remexre joined #forth 11:30:10 --- quit: webchat9 (Ping timeout: 260 seconds) 11:57:07 --- join: Zarutian_HTC joined #forth 14:42:37 --- quit: xek__ (Ping timeout: 240 seconds) 15:24:10 --- quit: WilhelmVonWeiner (Ping timeout: 240 seconds) 15:25:47 --- quit: gravicappa (Ping timeout: 256 seconds) 15:59:23 --- quit: john_cephalopoda (Quit: Leaving) 16:09:15 --- quit: dddddd (Ping timeout: 256 seconds) 16:14:23 --- join: dave0 joined #forth 17:03:48 --- quit: Keshl (Ping timeout: 256 seconds) 17:13:52 --- join: Keshl joined #forth 18:11:58 --- join: rdrop-exit joined #forth 18:48:39 --- join: jsoft joined #forth 18:53:31 --- join: boru` joined #forth 18:53:34 --- quit: boru (Disconnected by services) 18:53:37 --- nick: boru` -> boru 19:06:17 --- quit: Zarutian_HTC (Ping timeout: 240 seconds) 19:10:05 back 19:13:08 --- join: iyzsong joined #forth 19:16:50 --- join: WickedShell joined #forth 19:36:26 tabemann, how do you use your assert word ? 19:38:39 assert 19:38:56 if is zero, then is raised 19:39:10 hi tp and tabemann 19:39:18 hey guys 19:39:20 I've read the source but cant find what a valid exception name is 19:39:46 that's because you need to read the kernel source 19:39:47 hey rdrop-exit! Zen Guru of Forth 19:40:00 but don't worry, you can make up your own exceptions 19:40:08 hi Forth Master Technician (tm) 19:40:26 tp is an exception ;-) 19:40:36 like : my-exception space ." this is my exception" ; 19:40:39 yeah and it's syntax is 'pita' 19:41:19 tabemann, that looks like a ordinary definition ? 19:41:27 it is 19:41:35 exceptions are ordinary words in zeptoforth 19:41:49 all they do is print a useful message to the user 19:42:32 i find that confusing, when is a string a exception ? 19:42:48 tp, it's a fallback exception handler 19:42:57 yes 19:43:03 expecially when a hardware exception makes very terminal things happen 19:43:05 it's called if the exception is never caught 19:43:36 you can intercept the exception in your code and do what you think is appropriate 19:43:51 yes 19:44:07 ok, Ive just learned a new thing :) 19:44:11 if you don't the exception eventually percolates up to the outer interpreter 19:45:05 like you can do things like : catch-my-exception try dup ['] my-exception = if drop ." caught my exception" 0 then ?raise ; 19:46:07 this catches my-exception and prints a useful message, otherwise it passes the exception into the next exception handler 19:46:22 *onto 19:46:29 0 1 = assert my-exception this is my exception ok 19:46:44 ok, got it 19:48:07 there's something funny about that - it shouldn't be printing "ok" 19:49:16 thats at the terminal 19:49:28 Not all Forths have an "ok" prompt 19:49:34 oh you entered after the message appeared 19:49:53 rdrop-exit's doesnt because it isnt 'ok' 19:50:02 tabemann no 19:50:28 My Forths aren't line-oriented 19:50:29 okay, I just checked 19:50:31 tabemann I entered this "0 1 = assert my-exception" 19:50:49 in my exception handlers I normally put a CRLF at the end of the exception string 19:51:25 i would too usually 19:51:27 I prefer "averts" and "triggers" 19:51:42 but the ok wouls still be there just below the message 19:52:21 averts problem-exception 19:52:33 what's triggers for? 19:52:37 triggers problem-exception 19:53:15 different conditional 19:53:20 assert is kinda confusing in a way, so I'll adopt that scheme 19:53:38 assert normally in most languages raises a special assertion exception 19:54:54 I have a 'assert' but it's a technicians assert not a programmers one 19:56:05 as a tech Im concerned with making sure that registers are doing what I tell them to do, and thats where I use my assert 19:56:42 AVERTS raises on 0 19:56:54 TRIGGERS raises on non-zero 19:57:16 I use whichever goes most naturally with the logic 19:58:06 that comes before it 19:59:01 I use AVERTS more often than TRIGGERS overall 19:59:33 but sometimes TRIGGERS is more natural 20:02:46 averts 20:02:53 ;-) 20:03:53 triggers 20:04:18 :-)) 20:08:58 I also have SUPPRESS for suppressing an exception 20:09:23 try something SUPPRESS panic 20:10:12 TRY SUPPRESS panic 20:16:18 here's an example, when your interpreting from the keyboard rather then loading from a block or file, you might want to just beep when the user makes a typo instead of printing an error message 20:17:02 : deflect ( e|0 -- ? e| ) 20:17:02 ?dup 0; suppress xundefined suppress xnan ?raise beep ; 20:18:16 the above example suppress the undefined word exception and the not-a-number exception and beeps instead, other exceptiions proceed as normal 20:18:27 back 20:18:37 * suppresses the ... 20:18:49 ddd 20:18:55 whoops 20:19:28 ddd? triggers whoops 20:20:53 the "?dup 0;" is not neccessary, it's an optimization 20:36:03 right now the kind of optimizations I'm aiming for are memory ones, not processor time ones 20:36:38 specifically with regard to compiled code 20:38:00 --- quit: WickedShell (Remote host closed the connection) 20:39:46 the most effective way to minimize target footprint is to use a tethered Forth 20:40:34 --- join: WickedShell joined #forth 20:43:32 nothing goes on the target that isn't needed on the target for the target application 20:45:23 * tabemann likes to be able to just connect to the board with an MCU and make it do stuff 20:46:35 *connect to the board with a terminal 20:49:32 if you use a JTAG tether you can make your board do stuff right away, no need to install anything on the board 20:50:14 and you don't need a terminal on your PC, just use your PC forth 20:51:14 * tpbsd hopes tabemann will make a tethered cortex-m Forth 20:52:18 rdrop-exit, tethered only removes the overhead of the kernel 20:52:34 my real problem isn't the kernel's size but rather the size of the code generated from forth 20:52:48 no, all headers and the outer interpreter can be on the PC 20:52:48 this is not an issue that'd go away with going tethered 20:54:14 my problem is that the compiled forth code is far more voluminous than the assembled kernel code - even though the assembled kernel code is also full of headers, because it's meant to be callable from forth 20:56:29 you don't need headers on the target if your using a PC Forth instead of a terminal program to talk to the target 20:56:43 * you're using 20:57:08 as I said, the headers aren't why the code's taking up so much space 20:58:02 because the kernel also contains headers, yet is far more feature-dense than the compiled code 20:58:56 anyways, I need to get to bed 20:58:57 bbl 20:59:07 it's not just headers, it's everything related to the outer-interpreter and compiler 20:59:45 goodnight tabemann 21:00:11 when I say kernel, all of those things are part of it, because they need to be in the kernel can compile anything to begin with 21:00:50 *so it can 21:00:52 you compile from your PC, just replace your PC terminal program with a Forth 21:01:16 anyways, bedtime for real now 21:01:26 stay healthy 21:02:19 no terminal required, no gnu target tool chain required, just your PC Forth 21:02:40 rdrop-exit, as a user of both on-board and tethered forth, I'm with you on the advantages of a tether 21:03:58 the tethered Forth I have can produce a 100 byte bootable binary blinky, thats so small Gcc would probably not compete 21:04:14 what I find strange is that commercial Forths have been tether oriented for 30+ years, but open source Forths are very rarely tethered 21:05:42 actually more like 35+ years 21:06:20 I dont know why that is, but I have observed that there are hardly any OSS cortex-m forths 21:07:06 Mecrisp-Stellaris is the best by far and the *only* current and maintained OSS cortex-m Forth out there 21:07:12 --- quit: dys (Ping timeout: 264 seconds) 21:07:43 tabemann's is coming along nicely, his progress would give SARS-CoV-19 a run for it's monery! 21:07:52 but it's far from finished 21:07:54 I suspect ARM is a pita target 21:08:51 perhaps, plus most Forth writers are programmers and have no hardware experience. cortex-m doc is *massive* it scares many away 21:09:34 Even x86 is massive nowadays 21:09:46 it scares most hobbyists away, thats why old obsolete 8 bit chips like Atmel MEGA328 are still so popular 21:10:33 the only stable, non crashing x86 Forth I have any confidence in is Retro 21:11:12 or Mecrisp-Stellaris under QEMU 21:11:44 Ive tried almost every Forth out there and many are unfinished, slow, crashy junk 21:12:16 and a lot are so old now, they cont compile on a modern system 21:12:22 cont = wont 21:13:06 It's easier to make one's own than to rely on a hobbiest's experimental Forth 21:13:24 maybe for you 21:13:58 but I'm slowly coming to that same belief 21:14:13 that's only because you started Forth very late 21:14:32 yeah, I was 60 at the time 21:14:42 exactly 21:15:17 but Ive been designing and deploying micros since 1974 along with machine code, assembly lang etc 21:15:18 if you had started early, you would have a Forth that evolved with you over decades 21:15:29 but Im still not a programmmer, Im a tech 21:15:37 ahh thats a good point 21:15:41 ok you win! 21:18:44 how many people can say they know every aspect of their development environment intimately and it's perfectly adapted to their needs 21:19:06 that's the payoff 21:19:41 and they can change anything they want 21:20:47 I'm 100% with you there 21:21:32 Ive been satisfied that I can build my own dev system and make small changes to my tethered and on board forths so far 21:22:08 A new Forther could start with an simple minimal Forth like eForth, and if they cycle between using and adapting it over years, they'll end up with a Forth uniquely suited to their needs 21:22:31 the more they use it, the better it becomes 21:23:22 the problem is most new Forthers bite off more then they can chew and try to make the ultimate Forth right off the bat when they barely understand what they're doing 21:24:35 I've noticed that 21:24:46 if I make a Forth it will be really basic 21:25:04 I dont need advanced maths or graphics 21:25:14 I just twiddle bits in registers 21:26:40 the best way to build a sophisticated system is to evolve it from a small system that works 21:27:13 "evolve" being the key word 21:28:05 that makes perfect sense 21:28:17 darn it, I'm actually interested now 21:28:24 I forget who said that, I'm paraphrasing 21:28:54 Making a Forth is a fascinating learning experience 21:29:07 to a programmer! 21:29:23 it would probably be a frustrating experience for me 21:29:29 Im a hardware guy 21:29:39 to anyone who likes to have a deep understanding of their tools 21:31:01 well I do, but the programmer mindset is different to mine 21:31:15 I love the tech manuals that programmers generally hate 21:33:06 some programmers 21:33:25 mostly those who see programming as abastraction 21:33:35 * abstraction 21:38:45 the typical programmer mindset is not that useful for Forth anyway, I wouldn't worry about it think of your Forth as a device 21:40:22 "We shape our tools, and thereafter our tools shape us." -- Marshall McLuhan 22:02:56 tpbsd, typical programmer mindset doesn't fit forth so well. You just need the mindset of a creator. Someone who deals with the reality of their environment rather than pure abstractions. Hardware guys often take to it easier as rdrop-exit points out. 22:06:59 --- quit: iyzsong (Quit: ZNC 1.7.1 - https://znc.in) 22:07:21 --- join: iyzsong joined #forth 22:09:30 proteusguy, well in that case I'll get by :) 22:09:44 :) 22:10:18 but I have noticed that programmers always consider easy, the things I find very hard 22:10:27 it's a different mindset I think 22:11:22 and what you consider obvious is baffling to them 22:11:30 that's just lack of experience 22:11:40 thats true 22:12:15 but I've learned just assimilating the terminology a challenge 22:12:48 and of course the reverse is also true for a programmer when it comes to hardware 22:13:07 remember the chrysler 'lean burn engine" ? 22:13:14 every domain has its impenetrable jargon 22:13:35 at one point during it's development the mechanical and electronics teams were not on talking terms 22:13:59 each team truly believed the other team was bullshitting them 22:14:13 because their fields were so different 22:14:49 there's a story about when Raskin was designing the Canon Cat 22:16:08 He repeatedly explained that he didn't want an on/off switch and made a point of it in all design documents and diagrams 22:16:37 The prototype arrived with an on/off switch, someone assumed there was a mistake in the docs 22:17:07 hahah, so typical 22:17:13 lunch is on the table, catch you all later, stay healthy 22:17:22 --- quit: rdrop-exit (Quit: Lost terminal) 22:22:46 cya 22:23:10 https://www.youtube.com/watch?v=1gwGkQPnNOo <-- this surgeon is awesome 22:23:14 re SARS-CoV-19 22:24:37 tpbsd, I suspect that you will do just fine. :-) 22:25:18 proteusguy, I get by thats for sure. I find Forth incredibly easy to make gear with 22:25:51 no way I'll ever bother using enything else in embedded before SARS-CoV-19 takes me in the next few months ... 22:26:42 Ill have one regret as Im drowning in my own fluids, "why did I way till I was 60 to start using Forth ???" 22:26:49 :) 22:36:17 --- join: webchat9 joined #forth 22:36:58 hahaha 22:38:01 proteus-guy, I have found that I can do anything with Forth and if I get stuck, forthers are pretty helpful people :) 22:45:10 --- quit: iyzsong (Quit: ZNC 1.7.1 - https://znc.in) 22:47:12 --- join: iyzsong joined #forth 22:53:53 yeah this channel has some good folk 22:54:50 --- join: gravicappa joined #forth 22:55:00 yeah, it's a fantastic channel 23:01:16 --- quit: reepca (Read error: Connection reset by peer) 23:01:56 --- join: reepca joined #forth 23:07:00 --- quit: WickedShell (Remote host closed the connection) 23:59:59 --- log: ended forth/20.04.03