00:00:00 --- log: started forth/15.03.19 00:15:57 --- join: ehaliewicz (~user@50-0-50-238.dsl.dynamic.fusionbroadband.com) joined #forth 00:21:01 --- quit: ehaliewicz (Ping timeout: 272 seconds) 00:52:36 --- quit: MrMobius (Ping timeout: 246 seconds) 00:55:52 --- join: MrMobius (~Joey@c-68-45-16-225.hsd1.nj.comcast.net) joined #forth 01:18:59 --- quit: proteusguy (Remote host closed the connection) 02:11:27 --- join: Keshl_ (~Purple@24.115.181.94.res-cmts.gld.ptd.net) joined #forth 02:12:20 --- quit: Keshl (Disconnected by services) 02:12:21 --- nick: Keshl_ -> Keshl 02:26:27 --- join: nighty-_ (~nighty@hokuriku.rural-networks.com) joined #forth 02:41:37 --- join: proteusguy (~proteusgu@183.89.92.186) joined #forth 02:41:37 --- mode: ChanServ set +v proteusguy 02:44:10 --- join: true-grue (~grue@95-27-155-190.broadband.corbina.ru) joined #forth 02:54:30 --- quit: nighty-_ (Quit: Disappears in a puff of smoke) 02:59:08 --- join: nighty-_ (~nighty@hokuriku.rural-networks.com) joined #forth 03:05:05 awake again... :) 03:31:09 --- quit: mnemnion (Remote host closed the connection) 03:38:07 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 03:56:41 --- quit: mnemnion (Remote host closed the connection) 04:21:56 mark4: don't worry I will continue with forth despite Asau's opinion. I really like the simplicity of stack machines and I think forth is natural in stack machines so at least I will give it a good try. :) 04:22:54 * Keshl becomes 'that guy' and jumps in late. "Hardware used to natuvely run Forth? Why has nobody told me this? Where can I buy this stuff? Somebody take my money. o_o" 04:29:17 --- join: vsg1990 (~vsg1990@cpe-67-241-148-119.buffalo.res.rr.com) joined #forth 04:37:47 --- join: xyh (~xyh@2001:250:3002:5550:6ea1:cc0f:bcb2:b187) joined #forth 04:42:09 Keshl: I'm not buying anything I'm just doing my stack machine in VHDL with and FPGA as a pet project. 04:43:28 but the other points are correct. xD 04:47:20 I want this. I want an army of this. o_o 04:47:31 MUCK's on catapiller chips! OωO! 06:20:27 --- join: impomatic (~chatzilla@61.205.125.91.dyn.plus.net) joined #forth 06:23:11 --- join: johnmark_ (~johnmark@c-73-51-235-57.hsd1.il.comcast.net) joined #forth 07:02:59 --- quit: xyh (Remote host closed the connection) 07:49:39 --- join: mark4 (~mark4@38.122.200.194) joined #forth 07:53:46 --- join: yoplaid (~AndChat69@31.4.237.26) joined #forth 07:54:11 --- quit: gabriel_laddel (Remote host closed the connection) 07:54:59 --- quit: darkf (Quit: Leaving) 07:56:02 --- quit: yoplaid (Read error: Connection reset by peer) 07:56:15 --- join: yoplaid (~AndChat69@31.4.237.26) joined #forth 07:57:01 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 07:58:32 --- join: xyh (~xyh@2001:250:3002:5550:6ea1:cc0f:bcb2:b187) joined #forth 08:00:21 Hi there 08:00:46 ionthas_: navidad 08:01:28 --- quit: mnemnion (Ping timeout: 244 seconds) 08:06:50 --- join: AndChat|69225 (~AndChat69@31.4.237.26) joined #forth 08:06:57 --- quit: yoplaid (Read error: Connection reset by peer) 08:11:23 --- join: ehaliewicz (~user@50-0-50-238.dsl.dynamic.fusionbroadband.com) joined #forth 08:12:52 --- quit: proteusguy (Read error: Connection reset by peer) 08:17:19 --- join: proteusguy (~proteusgu@183.89.92.186) joined #forth 08:17:20 --- mode: ChanServ set +v proteusguy 08:24:06 --- join: yoplaid (~AndChat69@31.4.237.26) joined #forth 08:24:09 --- quit: AndChat|69225 (Read error: Connection reset by peer) 08:27:19 --- quit: yoplaid (Read error: Connection reset by peer) 08:27:34 --- join: yoplaid (~AndChat69@31.4.237.26) joined #forth 09:02:09 --- quit: yoplaid (Read error: Connection reset by peer) 09:02:52 --- join: yoplaid (~AndChat69@31.4.237.26) joined #forth 09:11:16 --- quit: xyh (Remote host closed the connection) 09:26:10 --- quit: ehaliewicz (Ping timeout: 244 seconds) 09:26:19 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 09:36:35 --- join: Zarutian (~Adium@168-110-22-46.fiber.hringdu.is) joined #forth 10:13:18 --- quit: yoplaid (Read error: Connection reset by peer) 10:13:19 --- join: AndChat|69225 (~AndChat69@31.4.237.26) joined #forth 10:19:49 --- join: xyh (~xyh@2001:250:3002:5550:6ea1:cc0f:bcb2:b187) joined #forth 10:40:09 --- join: ehaliewicz (~user@204.11.226.50.static.etheric.net) joined #forth 10:43:32 --- join: carc_00 (~carc@2001:41d0:52:cff::f85) joined #forth 10:45:45 --- quit: carc (Ping timeout: 256 seconds) 10:46:27 --- quit: AndChat|69225 (Read error: Connection reset by peer) 10:46:40 --- join: yoplaid (~AndChat69@31.4.237.26) joined #forth 10:47:58 --- quit: yoplaid (Read error: Connection reset by peer) 10:48:00 --- join: AndChat|69225 (~AndChat69@31.4.237.26) joined #forth 10:48:21 --- join: MrMobius_ (~MrMobius@149.160.204.55) joined #forth 10:56:39 --- quit: Keshl (Quit: Konversation terminated!) 11:08:12 --- quit: AndChat|69225 (Read error: Connection reset by peer) 11:27:05 What is the standard stack size for FORTH-83? 12:22:03 cell size or depth? I assume you're asking about depth. I do not know. 12:23:34 it may not be speicified, or just guaranteed to be at least X 12:26:35 I was referring to depth. I didn't see it in the specification. 12:27:17 I want to attempt to write a FORTH implementation for my PIC microcontroller. 12:35:47 i'd advise to use whatever stack size makes sense - standards are nice but seem to be mostly ignored for forth by ppl in this chan 12:36:51 Alright. My project is still in it's infancy stages. Not sure how I'll connect a keyboard to the PIC yet. 12:37:06 90% of the time no one says anything in this channel while I'm in here lol 12:37:08 it should be trivial (i hope) to change the stack size later 12:37:49 it's hit or miss. many people from different time zones, and a lot of lurkers who will chime in only if they're interested in the convo ;) 12:38:13 Well I really appreciate the advice. Thanks. :) 12:38:26 re: keyboard you could wire it up to a standard ps2 kbd and bit-bang the pins 12:39:04 I thought that would be the best bet, considering I have a lot of those keyboards lying around. 12:39:11 i'm in the middle of my own bare-metal OS/forth for x86 and finding a lot of misinformation and errors around keyboard information, so beware 12:39:24 cross reference, test, and verify for yourself 12:39:32 Definitely 12:39:44 good luck! 12:39:53 Thanks 12:43:52 vsg1990: at least 32 cells per stack is the rule I heard. 12:44:27 Zarutian: I'll make a note of that. Thanks! 12:44:58 vsg1990: and I hope that you are using PIC32 controler and not PIC16 or PIC12 (those are too limited for Forth I gather while the PIC32 which is a MIPS arch is big enough) 12:45:30 I haven't really selected the exact MCU I'm going to use. I do have a few of each though. 12:46:24 that main thing limiting the PIC16s is the data memory 12:46:59 Right. I think it would be possible to use them, but would require a quite a bit more code to get working. 12:47:11 another option than a keyboard, if there's a serial port is to use a null-modem cable to a computer/terminal, this usually requires very minimal driver code too 12:47:49 +1 for serial - it also gives you an output method w/o having to drive a LCD, LED bank, etc. 12:47:50 and it allows code block transfers 12:48:16 phadthai: I like that idea as well. 12:48:25 "all for the low low price of *two* i/o pins!" 12:48:45 In fact, I'll start with that. 12:49:38 i don't know PIC - does it have built-in opcodes or support chips for serial or will you have to bit bang? 12:50:23 Well they have a UART which I can use for serial 12:51:22 They have ICs that can convert easy between the two. 12:54:04 --- quit: xyh (Remote host closed the connection) 12:54:17 --- quit: MrMobius_ (Ping timeout: 244 seconds) 12:57:37 dont get a PIC 12:57:45 you will start to hate it very very quickly 12:57:48 get an AVR 12:58:16 All I've ever used are PICs. I want to try AVR's. 12:58:55 any time ive written any code for PICs i had to turn off optizations (in c) if the program had more than 600 lines 12:59:08 after that the compiler always produced broken code if optimizations were turned on 12:59:12 always 12:59:29 and the skid bucket crap tells me microchip doesnt know how to make CPUs 13:00:01 AVR is a dream 13:00:26 you can get a atmega32u4 from adafruit for $20 13:00:34 mark4: I'll be giving AVR a try soon. The reason I don't think I've ever had that problem with PIC is because I program them in ASM. 13:00:35 but i would also suggest getting an avr dragon 13:00:39 AVR is a sweet processor for embedded work. Much better architecture for coders. PIC is quite primitive comparably. 13:00:55 vsg1990, you will stil have the skid bucket problem 13:01:04 AVR asm is nicer as well. 13:01:09 put breakpoint on address A. run code... cpu stops 2 opcodes after a 13:01:18 solution: add 2 opcodes after A 13:01:25 its called a skid bucket 13:01:38 if vsg1990 knows PIC it might be a good idea for his (?) first forth to be PIC - then learn AVR ? 13:02:00 i would not like to write a forth for PIC devices :) 13:02:12 bluekelp, yeah if you have enough memory you can do forth on pic but it is starved for resources. 13:02:15 i tried and failed to learn ARM/thumb + implement a forth; so i'm back with x86 for the moment 13:02:50 but hey - vsg1990: if you're up for the challenge the AVR are nice chips 13:03:04 bluekelp, learn ARM first. thumb (specially thumb2) is kinda difficult if you dont know arm 13:03:21 i have a arm and thumb2 version of isforth 13:03:26 bluekelp, you found ARM/thumb more difficult than x86? thumb is a PITA but straight ARM is cleaner than x86. 13:03:38 yes 13:03:43 the issue is i didn't have an ARM non-thumb disco board. i got the stm32f4 bc it was cheap and had nice things on it 13:03:56 once you have ARM asm figured out its not too difficult to transition into thumb2 13:04:04 ARM was cool. thumb took out some of the coolness but i was able to manage 13:04:08 i used my beagleboard xm 13:04:24 i got the inner interp loop working but when weird things happened when i moved word defs from flash to ram 13:04:44 might not even be an ARM/thumb issue - could be something with the chip i am not familiar with or doing properly 13:05:00 arm is not harvard arch 13:06:23 they were forth words i moved to RAM and even loading the (indirect) codewords to run next failed. they had unexpected values and i was not able to figure out why 13:06:32 bluekelp: I have no problem learning another ASM, I pick them up fast. 13:07:07 im 95% of the way thru porting my atmega32u4 forth to atxmega 13:07:18 vsg1990, if you can handle pic ASM you will certainly be able to pickup AVR or ARM quite easily. 13:07:20 the 32u4 forth was never debugged so i never got it working 13:07:30 then do for it! not sure if they have uarts (probably do) but there is a lot of nice functionality and support circuitry in a nice inexpensive package 13:07:38 but i have a atxmega256A3Bu xplained board here now 13:08:00 proteusguy: I will definitely give it a go, is it as easy to get free samples from Atmel as it is with Microchip? 13:09:41 erm 13:09:51 thers avrfreaks 13:09:54 they are a good source 13:10:01 atmel documentation is kind of messed up 13:10:07 I've never tried. :) The AVR devices are so cheap. Arduino is all over of course. 13:10:07 Thanks for all the information and advice everyone. It's nice to see some chat in this channel. I'll be back on in a couple of hours. Thanks again! 13:10:19 arduino sucks 13:10:32 --- quit: vsg1990 (Read error: Connection reset by peer) 13:10:39 --- quit: carc_00 (Ping timeout: 265 seconds) 13:10:55 mark4, arduino does exactly what it was designed for and makes a great cheap first AVR device that is well documented for its devices. 13:11:06 arduino is cheap and there is a lot of support/help and documentation 13:11:11 its c++ 13:11:29 it's not high powered and doesn't have much support circuitry but it's decent for a demo board for avr 13:11:50 i don't use the arduino software stack. you can use most normal avr tools w/it 13:11:50 im sorry but embedded development and object obfuscated c++ are mutually exclusive 13:12:20 i just implemented an xbee mesh for arduino. i needed an xbee shield and a wifi shield. coded for both of those and i ws out of ram 13:12:26 to me it's just a nice cheap AVR board that "plays nice" with the shields out there, etc. 13:12:29 and i had used 70% of the code space 13:12:44 done right i would have used about 500 bytes of ram MAX and 1/30 of the code space 13:12:45 mark4, 1) nothing about arduino requires C++. I've done a lot of ASM on the arduino. 2) C++ makes an excellent embedded langauge if asm & forth aren't appropriate. 13:13:03 proteusguy, i wrote my stuff in pure c but the libraries are c++ 13:13:18 i can't imagine their Arduino Studio or whatever it is called is useful for "real" applications. or anything more complex than a few functions. 13:13:18 bluekelp, yeah I just always viewed arduino as a cheap avr board. 13:13:28 i don't think i even used their libs. 13:14:02 i was given a week to develop an xbee mesh network. and i didnt have everything i needed till 3 days left 13:14:05 arduino is nice because you can start with their tools, or give it to someone else to learn - and use your own c/asm for development when they're not looking ;) 13:14:13 i implemented the entire xbee mesh network in 3 days 13:14:14 bluekelp, yes I always went straight to the gcc toolkits. 13:14:38 did not have any choice, had to use certain libraries or i would have taken a lot longer 13:15:10 im moving the mesh network to raspberry pi 2's now 13:15:27 but i also need to implement ble obeservers and a ble advertiser 13:16:01 they wanted me to do all this on an arduino. i dobut that entire application would fit on an uno, maybe a mega not sure 13:16:47 im not very fond of atmels documentation or their libraries, they totally ignore the asm coder 13:17:26 but thats ok, im only using their ide to bootstrap my kernel. i need to be able to single step the primitives and see they do what i think they do lol 13:17:32 i already have my own avr assembler in forth 13:17:50 ill be using that to do the actual target build of the avr forth 13:34:50 --- join: carc (~carc@unaffiliated/carc) joined #forth 13:37:46 --- quit: carc (Client Quit) 13:38:02 --- join: MrMobius_ (~MrMobius@149.160.206.149) joined #forth 13:38:49 --- join: carc (~carc@unaffiliated/carc) joined #forth 13:46:20 --- join: gabriel_laddel (~user@unaffiliated/gabriel-laddel/x-9909917) joined #forth 13:46:54 mark4: I agree with you that c++ isnt suitable for embedded programming (or any programming for that matter imnsho) 13:49:24 exactly 13:49:40 i consider just C mutually exclusive with embedded devel 13:51:06 C is okayish for explaining some algorithms to some people but why people insist on using Algol68 syntax derived programming lanuages still, baffles me 13:58:00 --- quit: carc (Ping timeout: 265 seconds) 14:00:28 --- join: carc (~carc@unaffiliated/carc) joined #forth 14:11:27 --- quit: gabriel_laddel (Remote host closed the connection) 14:12:47 --- join: Mat4 (~cz@ip5b41928f.dynamic.kabel-deutschland.de) joined #forth 14:12:52 hi all 14:24:57 hey Mat4 14:25:08 hi bluekelp 14:27:45 --- quit: MrMobius_ (Ping timeout: 244 seconds) 14:37:25 --- quit: true-grue (Read error: Connection reset by peer) 15:24:14 --- join: vsg1990 (~vsg1990@cpe-67-241-148-119.buffalo.res.rr.com) joined #forth 15:25:04 And I'm back. 15:33:09 are you done with your PIC/AVR forth yet? 15:35:18 Lol no. I wish I could do that. I just got in the door. 15:36:31 well hurry up we're waiting :D 15:38:18 a PIC Forth sound interesting 15:39:17 vsg1990 may be working on one. some are trying to pursuade to go AVR (though those already exist) 15:39:37 I should probably just stick with PIC because I don't know of any implementations. 15:39:46 I could always do AVR later. 15:40:15 vsg1990: do you know how any other forths are implemented? 15:40:32 i did not and found i hit a stumbling block once i got to the compiler 15:40:57 Minimally. I wrote a small compiler in college for a subset of C, but that was a few years ago. 15:41:00 --- quit: Zarutian (Quit: Leaving.) 15:41:03 i recommend looking at how others are implemented to get a feel for the "soul" of forth - though diff forths can be implemented quite differently 15:41:37 i was amazed at how simple and elegant it could be - esp compared to my naive attempt 15:41:59 Hmm, any you recommend off the top of your head? 15:42:00 i can only recommend jonesforth (x86, though iirc ported to others) bc it's the only one i have (yet) studied 15:42:13 I'll take a gander at it. 15:42:16 it has the advantage of being very well documented (almost literate style) 15:42:50 it's not a very "good" forth, according to many. i think execution speed and lack of cool features are the primary complaints but i dont' want to speak for others 15:43:27 it is an "indirect threaded" forth. which has advantages and disadvantes. for your PIC, the space savings may make that a plus 15:43:52 OK. 15:44:33 anyway, it helped me grok how internally consistent a forth can be, esp compared to my "microforth" which was mostly custom x86 asm - whereas jones (and other "true" forths) tend to jump "into forth" ASAP 15:44:48 so the primitives of forth itself tend to be forth words (implemented in asm) 15:45:40 anyway. that's a long-winded way of just saying "research a little, it'll help". i tried making one based only off of Brodie's "Starting FORTH" 15:46:24 I have that book!, I got a copy for a few bucks on Amazon. 15:49:33 it's good for learning forth. a fun read. it didn't help (much) understand how forths are implemented under the hood (or i was too dense to glean more than a few concepts) 15:50:33 conditionals, loops, etc. and the compiler were all a mystery to me until i read how jones did it 15:52:18 jones forth bah 15:52:24 /me sulks 15:52:35 jones forth sources are a cluster **** horrendous mess 15:52:44 isforths sources are VERY well presented :P 15:53:00 vsg1990: If your environment is memory constraint, then a token-threaded Forth would be advantageous 15:53:10 mark4 does not like jonesforth at all. he is the primary hater of it that i have encountered 15:53:21 mark4: I don't believe isforth.com is hosted anymore. 15:53:27 i have not read isforth sources yet, so i could not recommend it 15:53:31 Mat4: Thanks, I'll research that. 15:53:33 i dont really hate it, i just hate that HE is getting all the credit! isforth was running in linux YEARS before he came along 15:53:48 and he just puked all his sources into one huge unreadable blob of source code 15:54:09 mark4: do you have a ref to token threaded? is it just replacing codeword addrs with (smaller) lookup table indexes? 15:54:11 i factored all the logical parts of a forth system out into very neat, very clean, VERY COMMENTED sources 15:54:28 oops - Mat4 ^^^ i meant you 15:54:50 bluekelp, i have never done token threading, i had considered it for the AVR but went with subroutine threading 15:55:14 token threaded isn't one of the "big three" i am aware of. i'll google around for info 15:55:27 bluekelp: primary yes 15:55:52 i considered token threading because this AVR has 24 bit addresses 15:55:53 mark4: i actually *liked* the "top-to-bottom, one file" aspect of jones. i don't believe it's necessary the best, but i did find it easy and "linear" to learn from 15:56:11 i could reduce those to 16 bits and keep the entire forth 16 bits by doing token threading 15:56:16 but again, i might like isforth once i dig into it 15:56:31 the performance disadvantage can be compensed though compilation of code sequences before execution 15:57:09 bluekelp, ill have to reinstate my domain registration lol 15:57:31 mat4 theres not much difference betwen token and indirect threading for performance 15:57:46 in fact i consider token threading just an alternate form of indirection 15:58:10 for the AVR (and PIC?) there is some overhead because of an additional conditional branch 15:58:46 sorry, I mean indirect branch 15:58:50 mark4: i was able to pull down a copy before it went away, though it may be a tad old 15:58:59 it would be an LPM of 16 bits into the Z register followed by an ijmp 15:59:09 iirc i even shared it w/someone who was asking. sry for distributing an older version :) 15:59:19 ive not updated in a while. been working on the not released arm/thumb2 versions 15:59:28 right now im doing my AVR forth because i want to use it at work 15:59:44 ok time to go home 16:02:32 --- quit: nighty^ (Remote host closed the connection) 16:05:29 --- join: nighty^ (~nighty@static-68-179-124-161.ptr.terago.net) joined #forth 16:06:07 --- quit: mark4 (Ping timeout: 272 seconds) 16:11:36 Does mark4 own isforth.com? 16:19:32 ciao 16:19:36 --- part: Mat4 left #forth 16:45:19 --- quit: nighty-_ (Quit: Disappears in a puff of smoke) 16:47:10 --- quit: ehaliewicz (Remote host closed the connection) 16:59:07 --- join: fugue (~fugue@gbc1124332.lnk.telstra.net) joined #forth 17:17:12 vsg1990: yes 17:17:25 I hope he puts the site back up, it's been down for a bit. 17:17:40 --- quit: joneshf-laptop (Ping timeout: 250 seconds) 17:17:42 i think he let is lapse but has been talking about bring it back 17:41:27 --- join: mark4 (~mark4@cpe-68-203-183-77.tx.res.rr.com) joined #forth 17:45:45 vsg1990: +1 for assembly. PIC18? 17:46:06 --- part: fugue left #forth 17:46:57 I have a lot of PICs, not sure which I'll use yet. I like my PIC16F690 and PIC18F4550 18:09:04 vsg1990: PIC: https://www.rfc1149.net/devel/rforth1.html http://flashforth.com/ http://pic18forth.sourceforge.net/ | AVR: http://krue.net/avrforth/ , avrforth is __completely__ in __gforth__. 18:10:52 Thanks! 18:15:56 --- join: saml_ (~saml@cpe-24-102-97-97.nyc.res.rr.com) joined #forth 18:24:14 --- quit: irsol (Remote host closed the connection) 18:32:18 --- join: irsol (~irsol@unaffiliated/contempt) joined #forth 18:36:05 --- join: ttmrichter (~ttmrichte@188.166.6.169) joined #forth 18:37:12 do pic has a mips aptiv serial chip? 18:41:06 yunfan: ? 18:46:42 DKordic``: i am interested of mips's aptiv serial 18:47:23 it looks like microchip is a big customer of mips, so i wonder if they have that 18:48:02 yunfan: I never heard of "aptiv serial". What is it? 18:51:14 --- join: darkf (~darkf___@unaffiliated/darkf) joined #forth 18:57:38 DKordic``: microaptiv interaptiv proaptiv search these 19:03:45 --- join: xyh (~xyh@2001:250:3002:5550:6ea1:cc0f:bcb2:b187) joined #forth 19:32:18 --- part: ttmrichter left #forth 19:34:35 DKordic``: got it? 19:40:05 --- quit: ASau (Ping timeout: 252 seconds) 19:42:56 yunfan: Yes. Apears in "PIC32 Family Reference Manual Section 50". 19:44:20 Stil don't understand what should "serial" mean. 19:44:23 DKordic``: so there're PIC32 chip with a microAptiv inside? 19:44:59 I guess. I don't know a specific device. 19:45:04 DKordic``: dont blame me, it should be `series` 19:45:17 I see :) . 19:45:56 i saw interAptiv have a LTE-target description, but didnt see any mobile phone use it 20:01:19 --- join: atommann (~atommann@58.251.2.94) joined #forth 20:04:55 --- join: nalaginrut (~nalaginru@203.192.156.9) joined #forth 20:25:41 --- quit: vsg1990 (Quit: Leaving) 20:41:19 --- join: joneshf-laptop (~joneshf@98.208.35.89) joined #forth 20:44:07 --- quit: johnmark_ (Quit: Leaving) 21:05:22 --- part: nalaginrut left #forth 21:23:51 --- join: kumul (~mool@adsl-72-50-86-20.prtc.net) joined #forth 21:37:58 --- quit: kumul (Quit: Leaving) 21:56:18 --- quit: saml_ (Quit: Leaving) 22:45:37 --- join: wolfskin (~AndChat38@95.131.169.236) joined #forth 22:45:42 --- nick: wolfskin -> Guest54595 22:46:32 --- quit: xyh (Remote host closed the connection) 22:48:06 --- quit: Guest54595 (Client Quit) 23:59:59 --- log: ended forth/15.03.19