07:08:11 --- log: started forth/04.09.17 07:08:11 --- join: clog (nef@bespin.org) joined #forth 07:08:11 --- topic: 'FORTH programming language. Info: http://forth.bespin.org/resources/introduction ANSI: http://www.taygeta.com/forth/dpans.htm FIG83: http://forth.sourceforge.net/standard/fst83/ Links: http://members.dsl-only.net/~loophog || Note: this chan is publicly logged. | misato' 07:08:11 --- topic: set by wossname on [Wed Sep 15 18:12:21 2004] 07:08:11 --- names: list (clog madwork_ onetom crc Serg_penguin mur tgunr jim @kc5tja cmeme warpzero Robert Frek skylan slava @ChanServ fridge arke Fractal) 07:08:30 --- quit: arke ("camping ... adios!") 07:23:09 --- quit: Serg_penguin () 07:42:44 --- quit: tgunr (Read error: 104 (Connection reset by peer)) 07:44:27 --- join: tgunr (~davec@vsat-148-63-4-107.c001.g4.mrt.starband.net) joined #forth 08:07:16 --- join: Herkamire (~jason@h000094d30ba2.ne.client2.attbi.com) joined #forth 08:07:16 --- mode: ChanServ set +o Herkamire 08:17:14 --- join: tathi (~josh@pcp02123722pcs.milfrd01.pa.comcast.net) joined #forth 08:21:25 --- quit: tgunr ("Leaving") 08:35:06 --- quit: tathi ("leaving") 08:44:16 --- join: wossname (~wossname@rn-v1w5a06.uwaterloo.ca) joined #forth 08:53:07 --- join: snowrichard (~richard2@adsl-068-209-159-248.sip.shv.bellsouth.net) joined #forth 08:54:37 --- quit: snowrichard (Client Quit) 09:03:03 --- join: arke (apache@11.198.216.81.dre.siw.siwnet.net) joined #forth 09:05:48 * crc has just finished RetroForth 7.4-beta 09:11:27 --- join: crc_ (crc@225-pool1.ras11.nynyc-t.alerondial.net) joined #forth 09:11:28 --- quit: crc (Read error: 104 (Connection reset by peer)) 09:11:38 --- nick: crc_ -> crc 09:12:44 crc: that's great :) 09:12:50 crc: what's the status on the bootable version? 09:13:32 Still about the same 09:13:59 I'll have hard drive support in place before 7.4 is offically released 09:14:41 I added my block editor to the mix; on the native version it'll be able to load/save blocks from the hard drive 09:14:54 cool :) 09:15:01 * crc is also making some progress on VESA support 09:17:23 VESA support should be ready by 7.5 (640x480 or 800x600; 256 colors) 09:17:49 cool 09:17:51 nice :) 09:17:54 Actually, VESA works, but the console doesn't support scrolling yet 09:17:57 we need more forths with graphics support 09:18:02 :-) 09:18:04 I agree 09:18:22 I'll still support text mode, but graphics are fun to play with 09:19:26 I'll probably support SVGALIB for similar graphics modes under Linux and FreeBSD as well 09:19:41 :) 09:20:11 have you considered SDL? 09:20:16 Yes 09:20:27 But it's a lot more complex to use 09:20:43 You have to lock/unlock the display buffer, etc 09:20:56 I don't really know much about svgalib, except that I'm pretty sure it doesn't work on my computer 09:21:04 I think it's x86 only 09:21:25 It basically sets the video mode, and gives you the starting address of the video memory 09:21:28 that's not hard 09:21:40 (It also has a lot of drawing functions that I don't use) 09:22:00 I just have: lock_video(); update_screen(); unlock_video(); 09:22:00 Maybe I'll just use the FB device driver... 09:22:14 but you do have to tell it to update the screen... 09:22:36 I prefer to directly manipulate video memory 09:22:42 yeah. 09:22:52 SDL is more general. Tries to cover many situations. 09:22:58 which I really appreciate, because I need some 09:23:11 IE my monitor does not support any other resolutions 09:24:09 Mine only supports some text modes, 320x200, 640x480, and 800x600 09:24:23 In the native versions I can only use 8-bit color 09:24:31 Though the video card can handle 32-bit 09:25:06 The card doesn't like linear modes with higher color depths :-( 09:26:06 How's the native herkforth going? 09:34:45 * crc is also redesigning the retroforth.org website 09:35:15 I should learn another language 09:35:23 why? 09:44:29 experience a different way of thinking about language 09:45:15 ok 09:47:42 crc I got it running in the pearpc emulator :) 09:48:28 it's really slow though. 09:48:30 and you cannot save 09:48:31 is this oric fellow ever in here? 09:48:48 ah, misread 09:48:53 http://oric.ifrance.com/oric/software.html 09:49:06 a fun page, anyway 09:50:44 --- quit: arke ("CGI:IRC (EOF)") 09:53:50 Herkamire: cool 09:54:20 --- join: qFox (C00K13S@82-169-140-229-mx.xdsl.tiscali.nl) joined #forth 09:54:36 * crc hopes to be running herkforth in PearPC soon 09:54:57 Is the slowness a problem with the emulator? 09:56:08 yeah 09:56:13 cursor movement is a real drag 09:56:24 might be better on x86 with the jit native compiler though 09:58:13 if your screen is at least 1024x768 you might be able to run pearpc bigger. 09:58:26 I bet most or all the blocks would fit on that terminal 09:58:46 18 lines or whatever is too little 10:02:28 I only have 800x600 10:02:53 Why can you only get 18 lines on PearPC? 10:04:22 as you can see: http://herkamire.com/downloads/hfpearpc.png 10:04:47 pearpc does not make efficient use of screen space for the OpenFirmware terminal emulator 10:05:23 I see that 10:05:26 800x600 gives 95x28 terminal 10:05:43 I use 10 or eleven lines for other things. 10:05:49 leaving 17 for the source 10:06:08 if that stupid logo wasn't so big, it would fit fine. 10:07:21 :) 10:10:10 Well, I'm looking forward to trying it :-) 10:11:00 * crc will have to go to bed soon... 10:22:48 --- quit: crc ("Time for bed... Goodnight!") 11:07:28 --- join: I440r (~mark4@216-110-82-203.gen.twtelecom.net) joined #forth 11:07:39 hi I440r 11:07:54 hi 11:07:58 <-- at work 11:08:17 this is lunch time so im at my desk -= been in class all week and today is the test lol 11:08:19 PANIC! 11:09:38 --- quit: wossname (Read error: 110 (Connection timed out)) 12:11:46 --- quit: qFox (Read error: 104 (Connection reset by peer)) 12:13:37 --- join: tathi (~josh@pcp02123722pcs.milfrd01.pa.comcast.net) joined #forth 12:15:26 --- join: wossname (~wossname@rn-v1w5a06.uwaterloo.ca) joined #forth 12:18:16 you'll do fine 12:18:41 just relax and concentrate 12:38:57 --- join: htp123 (~tehsux@S0106000d6151238b.gv.shawcable.net) joined #forth 12:46:49 --- join: qFox (C00K13S@82-169-140-229-mx.xdsl.tiscali.nl) joined #forth 12:47:07 Hi 12:47:48 hey 12:51:19 i'm trying to knock some sense into the java crowd by explaining dynamic languages: 12:51:19 http://www.javalobby.org/thread.jspa?messageID=91811054&threadID=14469&forumID=61 12:52:12 good luck :) 12:52:45 sun managed to drag a lot of c++ programmers about half way to lisp. 12:53:02 now somebody else should keep dragging them further :) 12:54:20 does anyone mind answering a quick forth question? 12:54:32 Well, I like your post. 12:54:36 I just did! 12:54:52 do you have another quick forth question? :) 12:55:35 how would you do this? : foo ' word ; ? 12:55:44 compile the xt of a word 12:55:48 ['] ? 12:55:51 maybe 12:56:06 hm, i guess that works. i was thinking maybe some word that compiles the current top of stack 12:56:16 [compile] 12:56:20 --- quit: Herkamire (Read error: 60 (Operation timed out)) 12:56:20 like, : foo [ ' word ] sp, ; or something 12:56:28 or , 12:56:41 htp123: I think : foo ['] word ; should work. 12:56:44 well, it would have to push it 12:56:51 no [compile] is for immediate words 12:56:59 oh yah? 12:57:08 it will just compile top of stack? 12:57:54 then running foo is the same as doing ' word 12:58:10 perfect. thanks 12:58:14 well, except that if you've redefined word in between, foo will have the old xt. 12:58:20 but I guess that's obvious... :) 12:58:21 yah 12:58:25 that's not an issue 12:58:34 what you want to do is get the address of do-literal (or whatever it's called in your forth), comma that in, then get the thing you want pushed on the stack and comma that in 12:59:10 ah ok. yah that makes sense 12:59:16 : foo [ (addr of doliteral) , ' word , ] ; 12:59:42 cool, thanks 12:59:43 but if there is a compiling word called (maybe) literal, you can use that 13:00:00 and it -should- do all that for you 13:00:14 what forth is this for? 13:00:14 would it just be ' word literal ? 13:00:23 maybe 13:00:31 just my own. im trying to learn forth by implementing it 13:00:33 you'd put that in brackets 13:00:37 ohh 13:01:00 htp123: direct threaded? 13:01:07 so how does your interpreter "compile" numbers to be pushed onto the stack? 13:01:51 it's for x86, and i store top of stack in edx, so i just compile a dup and then mov edx,value 13:01:55 --- join: Herkamire (~jason@h000094d30ba2.ne.client2.attbi.com) joined #forth 13:01:56 --- mode: ChanServ set +o Herkamire 13:02:32 can you encapsulate that in a word? 13:02:48 yah. something like doliteral? 13:03:28 or you could use a (previously suggested) direct approach, and write ['] 13:03:39 well, that doesnt seem very generic 13:04:00 i don't realy want to write [] versions of every word like that 13:04:06 yeah, I thought you were asking how to do it in an existing forth. 13:04:29 i sorta was. just how its done in general 13:04:37 so i can think of how to implement it 13:04:43 the factoring is up to you of course 13:05:05 there does exist ['] in some forths... 13:05:24 well, ' was just an example 13:05:33 i'd like something more general 13:05:39 so you really want a literal compiler 13:05:42 yah 13:05:48 my forths usually have a word ]lit 13:05:59 : foo [ ' word ]lit ; ? 13:06:03 yeah. 13:06:04 : ['] ' lit ; immediate (or something like that) 13:06:28 i like the ]lit idea 13:07:04 now, what if you had: : foo [ ' word ' word ]lit ; ? 13:07:10 would that compile only the last XT? 13:07:42 you could make the address of doliteral available somehow (but you seem to be doing that inline, so another choice is to have the word that compiles the literal simply inline the literal pusher) 13:07:59 htp123: yes. 13:08:37 I also just have a word lit (or maybe I spelled it out as literal) that takes the thing on top of the stack and compiles it as a literal. 13:08:43 and you'd have an extra item on the stack at compile time, a potential problem 13:08:45 what about something like this: : foo [ ' word1 ' word2 ] sp, sp, ; ? 13:09:19 where sp, is basically a call to literal 13:09:24 the sp, don't have to be immediate, in which case you'd do 13:09:41 : foo [ ' word1 ' word2 sp, sp, ] ; 13:10:01 ah ok 13:10:19 NOTE that word2 would be pushed -under- word1 13:10:31 ah, right 13:10:45 so for that you -could- do 13:10:55 : foo [ ' word1 sp, ' word2 sp, ] ; 13:11:13 that looks pretty good i think 13:11:29 though that's not a lot shorter than : foo compile word1 compile word2 ; 13:11:43 which (I think?) is what you do in an F83 system. 13:11:55 what exactly does compile do? does it compile the XT? 13:12:17 causes it to be ,ed when the foo is run 13:12:37 (not what you asked for :) 13:12:39 oh right. 13:12:40 ah ok 13:12:40 gah. 13:12:43 sorry 13:12:53 great, thanks a lot. that's more than enough to get me started :) 13:13:26 I wonder if Ragsdale's figforth installation manual is still around 13:16:17 If I recall correctly, some forths had a compiling word called LITERAL, and you'd use it like your sp, 13:17:03 hm, i kinda like sp, more. shorter 13:17:17 i guess its not a frequent issue though 13:18:07 that's true; it's only used in the compiler part of the interpreter 13:18:51 do you have separate compile and interpret loops? or do you have a variable called state? 13:19:02 i have a state variable 13:19:28 boss just arrived. gotta head 13:19:33 thanks for the help 13:19:41 have fun 13:20:41 since your client is still here, I'll finish this last sentence... 13:22:14 the section of your interpreter that recognizes a number would push it onto the stack and maybe (depending upon state) call LITERAL 13:23:39 or maybe it would call LITERAL unconditionally, and LITERAL would be the state-smart word 13:33:57 --- join: TheBlueWizard (TheBlueWiz@modem-046.nyc-tc03a.fcc.net) joined #forth 13:33:58 --- mode: ChanServ set +o TheBlueWizard 13:34:04 moi 14:02:14 moi! :) 14:02:21 Terve, TheBlueWizard 14:02:36 Robert hiya! 14:16:14 Good morning. 14:16:21 hi kc5tja 14:17:51 kc5tja hiya 14:18:37 Just woke up. 14:19:33 Doing the aikido-then-work thing is definitely going to work out! 14:19:47 cool 14:20:47 Already been to both classes this week. That rather shocked the other students. :) 14:21:33 Anyway, I rather need to get some food, so I'll ge afk again. 14:25:27 --- quit: Frek ("Client exiting") 14:33:17 --- quit: tathi ("leaving") 14:46:01 --- join: ianp (ian@inpuj.net) joined #forth 14:46:17 anyone happen to know a good place to go buy electronics in the chicagoland area 14:46:26 looking around sparkfun.com right now, neat stuff in there... 14:48:31 how's the kestrel? 14:51:49 kc5tja is AFK 14:52:24 his current state seems to be... 14:52:31 Doing the aikido-then-work thing is definitely going to work out! 14:53:43 ro ho ho 14:56:16 People giving their full attention to the commercials on TV scares me. 14:57:00 I do do that... but that's because I also have my finger on the FF button :) 14:57:36 anybody here familiar with sdl? 14:58:08 I've built it... but never read its docs or used functions in it 15:02:14 that's the video/sound/mouse thing, right? 15:02:29 (I think neverwinter nights used it) 15:02:47 yeah 15:02:51 its a simple framebuffer & input api 15:03:35 yeah, original statement stands... I dunno much about it beyond that 15:05:35 back 15:06:33 I've used it to implement the old Kestrel emulator. 15:06:54 ianp: See my website; Kestrel, as it originally stood, is dead. 15:07:17 No matter what I did, it would cost too much to produce, and therefore, would price itself clean out of its target market. 15:08:01 Nobody here is willing to purchase a Kestrel for $450 when for about half that they can purchase an x86 PC motherboard that runs 5x faster and has the latest technology on it. 15:08:47 What you need is a thousand chinese slave workers and a good marketing department. 15:09:09 and what you'll get is a railroad system? :) 15:09:32 what's a kestral, btw? 15:09:41 hmm 15:10:09 jim: http://www.falvotech.com/kestrel.html 15:13:11 does anyone have or is interested in arm7? 15:13:52 * kc5tja is considering ARM9 for a future generation of Kestrel designs. 15:14:04 But I'm far, far, far from even attempting any new designs right now. 15:14:10 Interfacing to SDRAM is nigh impossible. 15:14:17 why? 15:14:33 Because the logic used to drive them is insanely complex 15:15:07 hehehe from the sdl tutorial 15:15:09 "Look at your monitor very closely with a magnifying glass (note: you may hurt your eyes if you do it a lot)." 15:15:21 Not only that, but the RAM chips themselves *MUST* be tied to a particular chipset revision. 15:15:44 If I change from 256MB chips to, say, 1GB chips, that requires a whole new set of timing parameters. 15:16:26 which would require redesign of the ram interface? 15:16:43 These things must be (somehow) autodetected at startup, and the memory controller (yes, any system with SDRAM must have a distinct chunk of logic called the "Memory Controller") must be programmed accordingly, BEFORE THE CPU BOOTS. 15:17:30 Not so much a redesign -- pinouts of the SDRAM chips are consistent (thankfully). But that's about all. 15:17:42 is ddr similar in terms of that requirement? 15:17:58 DDR is SDRAM, so yes. 15:19:19 well, my simple sdl app to draw a gradient works. 15:20:24 * Herkamire applauds slava 15:22:04 are there single-chip sdram controllers? 15:22:04 that (a) detect ram type, and (b) program themselves accordingly? 15:22:14 did you use ffcall from gforth? 15:22:45 jim, no i just wrote a C program. i'll be writing an ffi for factor and as a first test attempt to reproduce the output of the C program. 15:24:41 reason I ask about arm7, is I recently saw the instruction set, it looked interesting... so I'm writing a simulator for it 15:25:05 i'll have to add some notion of a 'word array' to factor to directly access the framebuffer 15:25:22 hmm, or maybe i'll only expose a blitter and do the framebuffer stuff in C? 15:26:45 gotta go...all bye 15:26:52 jim: (a) no (b) yes. You typically need to have some other means of autodetection. 15:26:58 --- part: TheBlueWizard left #forth 15:27:47 so for (a) you need external logic which has to take over the (b) job 15:29:01 does sdram use notches in the pc board that operates switches in the ram socket? 15:29:15 in order to communicate ram type 15:31:26 kc5tja, ping 15:31:57 kc5tja, my ffi will be generating code to do the boxing/unboxing of factor types on the C stack, i think this will give performance equivalent to hand-coded primitive wrappers 15:33:58 --- quit: qFox ("this quit is sponsored by somebody!") 15:34:16 --- quit: wossname (Connection timed out) 15:54:02 --- join: Topaz (jonny@spc1-horn1-6-0-cust217.cosh.broadband.ntl.com) joined #forth 15:55:42 slava: pong 15:56:16 jim: No, they use hard-wired logic levels on dedicated pins to identify the kinds and capacity of the RAM chips. 15:59:47 so they do that instead of having a notched pc board 16:01:13 and so it's less a matter of -detecting- the type of ram (that job is done by those hardwired pins) and more a matter of just using that info 16:01:34 ( 2 ) "fuckwits" dlopen 16:01:34 ERROR: FFI: Shared object "fuckwits" not found 16:01:40 ( 4 ) "libX11.so" dlopen 16:01:40 ( 5 ) 16:01:44 good :) 16:01:51 so i can open .so's, now i need to do useful things with them :) 16:02:22 so is there complications in the programming of the sdram controller? 16:35:06 jim: The problem is the very existance of such controllers in the first place. 16:35:14 Using one is basically set it and forget it. 16:35:25 --- join: I440r_ (~mark4@216-110-82-59.gen.twtelecom.net) joined #forth 16:35:55 But SDRAM is not spontaneous -- accessing a single memory location can take upwards of around 16 clock cycles in some cases. 16:36:33 And with low clock speeds (double-digit MHz or less), that is a rediculous amount of time to spend fetching or storing data to memory. 16:39:01 my silly ARM (/me rambles on) can access SDRAM in 5 clock cycles (3 row/col + 2 CAS), and burst after that at one word/cycle 16:39:07 i'm quite looking forward to playing with it 16:42:24 you have an arm? :) 16:43:13 two, infact 16:43:15 *grin* 16:43:54 * jim has at least one and less than three :) 16:44:50 --- join: oldtimerelijun (~asdf@207.140.211.88) joined #forth 16:45:29 anyone see ChipChuck around here? 16:46:10 Yep, about a year ago. 16:48:23 what was his quit msg? 16:48:41 dammit, i think he was writing some new forth compiler 16:48:42 Haha 16:48:46 i needed to ask him about that 16:48:49 Mail him. 16:55:58 --- nick: oldtimerelijun -> redorc 17:01:16 colorforth? 17:01:51 ultraColorForth 17:01:59 some kind of improvement 17:02:01 oh yah? 17:02:02 witih like, a GUI and all 17:02:06 never heard of it 17:02:08 hm, really? 17:02:12 it's in development still 17:02:16 doesn't sound like a very chuck thing to do 17:02:18 hasn't been publically announced 17:02:31 weird 17:02:45 htp123: that's why it is so interesting. but needless to say the GUI will not be bloated in the slightest way 17:02:59 it's going to be like a hyper minimal thing similar to QNX's photon, i think 17:03:04 yah i would be interested in seeing that 17:05:00 how did you hear about this? 17:06:01 private conversation with ChipChuck 17:06:08 he not so much as told me but hinted at the possiblity 17:06:18 it's all pretty vague but i'm pretty certain he's working on something 17:06:29 interesting 17:06:31 i'm wondering if anyone else has more info on it 17:06:37 he must have told others about it 17:06:44 i was wondering what he's working on. colorforth hasnt been updated in quite a while 17:07:07 yah, not me though unfortunately 17:08:10 e-mail him :) 17:08:17 --- nick: redorc -> oldtimerelijun 17:10:58 he made some posts to the colorforth mailing list a while back 17:11:03 saying he was working on colorforth2 17:11:16 he was working on getting it to boot off some USB thumbdrive 17:11:29 I don't remember hearing anything about GUI though 17:11:50 wow, usb thumbdrive? 17:11:52 that's awesome 17:12:57 --- quit: oldtimerelijun (Client Quit) 17:14:39 Topaz: That is why I said "up to" 16 cycles. x86 architectures can access SDRAM in something like 4 to 8 typically. 17:14:50 ah, ok 17:14:57 Or, more accurately, the kind of SDRAMs they often use. 17:15:01 but yeah, SDRAM is irritating 17:15:06 Still though, it is most annoying. 17:15:52 and i'm not even going to be able to nick the cache off old motherboards, heh, the recent stuff i found is 'burst cache' 17:16:48 Topaz: Yes, synchronous SRAM. 17:17:07 heh, yeah 17:17:16 i guess that is the only way to make RAM go fast nowadays 17:17:21 with propagation times as they are... 17:20:36 --- quit: Topaz (Remote closed the connection) 17:31:47 Yep. 17:33:21 Anyway, this is wildly off the point, I think. 17:33:43 The reason I decided to cancel the Kestrel project is because there was no way in hell I could get it below the $150 mark wholesale. Just no way. 17:39:47 --- join: imaginator (~George@georgeps.dsl.xmission.com) joined #forth 18:31:46 doh :/ 18:32:05 sorry to hear that 18:33:05 stupid cost 18:35:15 --- join: snowrichard (~richard2@adsl-068-209-159-248.sip.shv.bellsouth.net) joined #forth 18:39:24 hello 18:40:04 --- quit: imaginator (leguin.freenode.net irc.freenode.net) 18:40:42 exit 18:40:44 --- quit: snowrichard ("leaving") 18:53:52 kc5 instead of scrapping kestrel why not increase to $200 ? 18:54:10 200 is not unreasonable for a decent machine 18:54:35 sc 18:58:25 l 18:58:27 argh 19:07:05 --- join: imaginator (~George@georgeps.dsl.xmission.com) joined #forth 19:08:45 I440r_: he said it would be $450 19:08:51 or thereabouts 19:14:19 c'mon brain! go go go! 19:14:27 can't program worth crap the past few days 19:17:02 not even following my own advice 19:22:43 --- join: snowrichard (~richard2@adsl-068-209-159-248.sip.shv.bellsouth.net) joined #forth 19:29:41 --- quit: snowrichard ("leaving") 19:29:46 Indeed; $450 for a slow, relatively unexpandable machine is just 4x too expensive as it is. 19:39:38 --- join: tathi (~josh@pcp02123722pcs.milfrd01.pa.comcast.net) joined #forth 19:46:22 Crap. I need to start getting ready for work, I guess. It's already 8PM here. 20:01:52 --- join: saon (Ecoder@c-24-129-95-254.se.client2.attbi.com) joined #forth 20:18:40 --- join: snowrichard (~richard@adsl-068-209-159-248.sip.shv.bellsouth.net) joined #forth 20:18:56 hello 20:19:47 --- quit: snowrichard (Client Quit) 20:27:16 --- join: snowrichard (~richard@adsl-068-209-159-248.sip.shv.bellsouth.net) joined #forth 20:28:30 --- quit: snowrichard (Client Quit) 20:35:50 --- join: madgarden (Madgarden@Kitchener-HSE-ppp3575812.sympatico.ca) joined #forth 20:58:49 --- quit: I440r_ ("bbl") 21:21:29 Off to work. 21:28:01 --- join: I440r_ (~mark4@216-110-82-59.gen.twtelecom.net) joined #forth 21:53:22 --- join: I4404__ (~mark4@216-110-82-205.gen.twtelecom.net) joined #forth 22:10:55 --- quit: I440r (Read error: 110 (Connection timed out)) 22:19:28 --- quit: madgarden (Read error: 60 (Operation timed out)) 22:24:50 --- quit: tathi ("leaving") 22:25:24 --- quit: htp123 ("*") 22:58:27 --- quit: Herkamire ("bed") 23:58:02 --- join: qFox (C00K13S@82-169-140-229-mx.xdsl.tiscali.nl) joined #forth 23:59:59 --- log: ended forth/04.09.17