00:00:00 --- log: started forth/03.03.04 00:12:09 --- quit: sma (adams.freenode.net irc.freenode.net) 00:12:09 --- quit: serg_log (adams.freenode.net irc.freenode.net) 00:12:09 --- quit: Robert (adams.freenode.net irc.freenode.net) 00:12:09 --- quit: Jim7J1AJH (adams.freenode.net irc.freenode.net) 00:14:23 --- join: Jim7J1AJH (~jwt@n1.dskk.co.jp) joined #forth 00:14:23 --- join: serg_log (~serg@h138n2fls31o965.telia.com) joined #forth 00:14:23 --- join: Robert (~snofs@h138n2fls31o965.telia.com) joined #forth 00:14:23 --- join: sma (stephenma@ashd174qy22og.bc.hsia.telus.net) joined #forth 00:39:53 --- quit: Speuler (Read error: 60 (Operation timed out)) 00:57:56 --- join: ramnull (~nicad@12-241-145-39.client.attbi.com) joined #forth 00:59:01 What's up? 01:16:19 --- join: Klaw (anonymouse@ip68-4-155-247.oc.oc.cox.net) joined #forth 01:23:57 --- quit: sma (adams.freenode.net irc.freenode.net) 01:23:57 --- quit: serg_log (adams.freenode.net irc.freenode.net) 01:23:58 --- quit: Robert (adams.freenode.net irc.freenode.net) 01:23:58 --- quit: Jim7J1AJH (adams.freenode.net irc.freenode.net) 01:24:50 --- quit: ramnull (Read error: 60 (Operation timed out)) 01:26:03 --- join: Jim7J1AJH (~jwt@n1.dskk.co.jp) joined #forth 01:26:03 --- join: serg_log (~serg@h138n2fls31o965.telia.com) joined #forth 01:26:03 --- join: Robert (~snofs@h138n2fls31o965.telia.com) joined #forth 01:26:03 --- join: sma (stephenma@ashd174qy22og.bc.hsia.telus.net) joined #forth 01:28:46 --- quit: Jim7J1AJH ("73 from Tokyo") 01:32:11 --- join: Speuler (~Speuler@mnch-d9ba4ab6.pool.mediaWays.net) joined #forth 01:39:28 --- join: Serg_Penguin (~Z@nat-ch1.nat.comex.ru) joined #forth 02:02:54 --- quit: Serg_Penguin () 02:32:55 --- join: ramnull (~nicad@12-241-145-39.client.attbi.com) joined #forth 02:33:24 What's up? Lurkers. 02:41:26 --- quit: Speuler (Read error: 60 (Operation timed out)) 03:04:27 lurk 03:21:42 --- quit: ramnull (Read error: 110 (Connection timed out)) 03:32:51 --- join: Speuler (~Speuler@mnch-d9ba4ab6.pool.mediaWays.net) joined #forth 03:34:29 --- join: ramnull (~nicad@12-241-145-39.client.attbi.com) joined #forth 03:39:44 The IsForth site doesnt seem to be working right. 04:04:15 --- quit: ramnull (Remote closed the connection) 04:10:31 --- join: Serg_Penguin (~Z@nat-ch1.nat.comex.ru) joined #forth 04:49:59 --- quit: Speuler (Read error: 60 (Operation timed out)) 04:51:45 --- join: Speuler (~Speuler@mnch-d9ba4ab6.pool.mediaWays.net) joined #forth 05:07:55 --- quit: Serg_Penguin (Read error: 110 (Connection timed out)) 05:49:25 --- join: Serg_Penguin (~Z@nat-ch1.nat.comex.ru) joined #forth 05:50:05 --- quit: Speuler (adams.freenode.net irc.freenode.net) 05:50:06 --- quit: sma (adams.freenode.net irc.freenode.net) 05:50:06 --- quit: serg_log (adams.freenode.net irc.freenode.net) 05:50:06 --- quit: Robert (adams.freenode.net irc.freenode.net) 05:51:58 --- join: Speuler (~Speuler@mnch-d9ba4ab6.pool.mediaWays.net) joined #forth 05:51:58 --- join: serg_log (~serg@h138n2fls31o965.telia.com) joined #forth 05:51:58 --- join: Robert (~snofs@h138n2fls31o965.telia.com) joined #forth 05:51:58 --- join: sma (stephenma@ashd174qy22og.bc.hsia.telus.net) joined #forth 05:56:36 --- join: TreyB (~trey@cpe-66-87-192-27.tx.sprintbbd.net) joined #forth 05:57:45 --- part: serg_log left #forth 06:10:27 --- join: gilbertdeb (~gilbert@fl-nked-ubr2-c3a-29.dad.adelphia.net) joined #forth 06:28:35 --- quit: Serg_Penguin (Read error: 110 (Connection timed out)) 06:37:43 --- quit: gilbertdeb ("Client Exiting") 08:34:00 --- join: gilbertdeb (~gilbert@fl-nked-ubr2-c3a-29.dad.adelphia.net) joined #forth 08:34:04 hello 08:52:25 --- join: I440r (~mark4@ip209-183-83-111.ts.indy.net) joined #forth 08:55:09 I440r: do you intend to doc all of iforth, or just the specifics, where iforth differs from, say "common forth" to avoid the word "standard" ? 08:55:15 someone fragged the clss.net web page after i updated it last nite :) 08:55:18 isforth, i mean 08:55:34 ill be documenting every word once i get started on that track 08:56:08 that means, i would make sense to have some kind of "common forth" doc, where many forths could refer to 08:56:27 hh 08:56:33 no need to doc "swap" over and over again 08:56:37 yea + - / * dont tend to differ :) 08:56:53 split your job 08:58:50 i was considering a net-based doc facility, on a per-word base 08:59:12 means, many forths could use parts of the same doc 08:59:44 would of course be possible to pack the doc into a local file 09:00:00 hmm 09:00:02 a doc generator 09:01:52 if forth-written, would double as online-help 09:02:05 local or net 09:02:26 united doc 09:02:30 an online help would be good 09:03:12 leaves more time for coding, less for documenting 09:03:28 heh 09:04:13 just the specifics 09:04:39 rest from common doc pool 09:05:14 could also call for "common forth" as a sub-standard 09:05:41 that what works all across ans, f83, f79, fig and isforth :) 09:05:49 it would mimic "ans" forth too much. 09:06:02 and people would expect every word documented there to be in ever forth - 09:06:10 would have to point out that that was not the case 09:06:31 if one implements non-standard behaviour, it is his task to doc it 09:06:37 i.e. "this is how THIS word USUALLY works if it is contained within which ever forth YOU are using" 09:06:51 well isforth is very very very non ans standard 09:06:52 if he fails people's expectation, it's not the common doc pool fault 09:07:09 correct 09:07:13 i wasnt saying that 09:07:22 but even ans standard forths differ vastly 09:07:33 where ? 09:07:42 their "swap" ? 09:07:44 not every word in one is contained within another 09:08:06 not sure whether you get the idea. it is not to doc one specific forth 09:08:19 that is , one specific ans implementation 09:08:20 will you be restricting your "common" forth to just ans core wordset ? 09:08:47 didn't say ans, except in "across ans, f83, f79, fig and isforth" 09:08:54 if you also include words from the 79 standard and the 83 standard you will find words with the same name and SIMILAR functionality 09:08:58 ok then 09:09:10 if not common, not in common doc pool 09:09:13 specific, then 09:09:26 ' 09:09:28 find 09:09:32 look at 79 standard not and 83 standard not and ans standard "invert" bleh 09:09:39 not 09:09:56 invert would be in the ans-specific pool 09:10:12 and "not" ? 09:10:17 differs between 79 and 83 09:10:20 in the 83-specific 09:10:38 which is why ans took the GAY route and defined "invert" 09:10:44 there's no not in ans, and bool/bit diff in 83/79 09:10:56 "invert" is ans's way of NOT taking a stand on any issue what so ever 09:11:00 can't put not into common doc pool 09:11:04 "lets not resolve this problem once and for all" 09:11:31 I440r: would you like to redefine ANS? 09:11:41 i'm not looking for the differences, but the commonities 09:11:53 perhaps ISforth could be come the first ANSisforth compliant forth :D 09:12:11 ansnotforth 09:12:32 the docs from eforth academy are quite readable. 09:12:40 I don't know if it meets your criterion speuler 09:12:50 gilbertdeb: i would rm -rf ans-forth 09:12:54 permanantly :) 09:13:01 many eforth words do for sure 09:13:01 I440r: and replace it with ... ? 09:13:13 isforth :) 09:13:24 i found the eforth dup working like f79 dup :) 09:13:24 isforth is 100% isforth standard compliant 09:13:27 Speuler: eforth's creator really documented it thorougly. 09:13:33 I like his docs. 09:13:46 I440r: have you seen bashforth? 09:13:54 it is 100% bashforth compliant :D 09:14:08 :) 09:14:17 but versions differ :O 09:14:19 word is non-standard ( c -- a n ) 09:14:32 find is probably too 09:15:38 there is a forth wiki no? 09:15:41 i'd put bash somewhere between ans and f83, which a few exceptions 09:15:46 accept is ans 09:16:05 throw catch is 09:16:22 accept is gay too. thers nothig wrong with query/expect 09:16:45 accept is cleaner 09:16:47 ( a -- n ) 09:17:14 query is a horror. 09:17:19 fixed buffer address 09:17:29 >in to find out len 09:17:35 nope 09:17:39 ahem 09:17:40 no fixed buffer address at all 09:17:51 i can't specify it on stack 09:17:52 tib is a variable pointing to the buffer 09:17:58 shudder 09:17:59 so ? 09:18:28 why not put address for ! into a var ? 09:18:32 var storeaddress 09:18:41 adr storeaddress ! 09:18:45 n ! 09:19:05 can't use ! for storeaddress :) 09:19:19 lets just invent problems eh :) 09:19:22 create storeaddress here , 09:19:31 adr storeaddr ! 09:19:34 n ! 09:19:40 *grin* 09:19:40 my tib is dynamic - my fload depends on this fact 09:19:43 same principle 09:20:10 yes "why invent problems" ? answer: query uses same "technology" 09:20:29 why use variable to point to buffer ? 09:20:45 I440r: how far along is isforth thus far? 09:21:03 bashforth has a fixed tib 09:21:07 what do you mean ? 09:21:17 bashforth should be TOTD as well Speuler. 09:21:23 I440r: is it finished? 09:21:38 TOTD ? 09:21:52 yeah look up there. 09:22:01 gilbertdeb: it wont be finished ever. but it will be "mostly" finished when i have an assembler and meta-compiler 09:22:01 where it says ultratech and all that. 09:22:10 and some documentation :) 09:22:20 No definitions found for "TOTD" 09:22:33 perhaps you mean: 09:22:34 web1913: Tod Tot Toted Toad Toed Told Tota Tote Toty 09:22:34 wn: tot toad Todd toed tote 09:22:36 topic of the day 09:22:39 ah 09:22:40 OTD == of the day. 09:23:04 TOTT 09:23:05 also the following: CM = chucky, ER = second forth programmer ... 09:23:15 totally over the top 09:23:23 TINSTAA = there is no such thing as a . 09:23:34 FM 09:23:34 eg TINSTAABL = there is no such thing as a beginners linux 09:23:35 :D 09:23:39 FL 09:23:45 FL? 09:23:48 forth loop? 09:23:49 free lunch 09:23:54 ah yes. 09:23:56 tinstaafl 09:24:15 SI 09:24:20 speuler island 09:24:22 hahah 09:24:26 TINSTAASI 09:24:34 well TINSTAAGI 09:24:53 but... TISATAA Gilbert Island. 09:25:08 TISATAA = there is such a thing as a 09:25:11 TIATAASI 09:25:21 no! 09:25:25 impossible! 09:25:26 where? 09:25:31 all around me 09:25:38 har har 09:26:23 I am beginning to understand a little the forth programming way. 09:26:32 good 09:26:33 you make words 09:26:38 and then you put words in 'sentences'. 09:26:42 what caused you to pick it up ? 09:26:53 oh, the lisp people. 09:27:01 I went there trying to learn lisp and they said learn forth. 09:27:08 hehe 09:27:13 so I came here. 09:27:18 and I got lost :D 09:27:45 less parantheses in forth 09:27:55 but it isn't just about parenthesis. 09:28:07 forth revolves around the dictionary and the stack. 09:28:28 hmm 09:28:31 by now I should be ready to write YAFT 09:28:35 YA= yet another 09:28:38 * Speuler thinks about writing bashlisp 09:28:44 CH 09:28:51 *CH = considered harmful 09:28:55 YAFTCH 09:29:01 FT=forth tut. 09:29:17 I couldn't get my mind around it w/o understanding asm. 09:29:25 and here I was thinking it was a high level language :D 09:29:38 it can be 09:29:44 can. 09:29:45 isn't. 09:30:00 is the tool to make higher level lang from it 09:30:07 it is a machine . 09:30:08 that's how you program 09:30:10 in forth 09:30:15 it is a VM 09:30:20 the final app is an app-specific language 09:30:27 high level 09:30:29 so in order to be a good forth programmer, you must be a good linguist :O 09:30:34 or an essayist! 09:30:35 it helps 09:31:00 also intimate knowledge of the machine beneath is helpful. 09:31:17 depends on the job. 09:31:21 not required 09:31:26 helpful. 09:31:36 Hah, BSD -> Debian? :) 09:31:56 Robert: alas. 09:32:08 it came to pass that BSD wouldn't go beyond the install. 09:32:21 I didn't know enough of ficl to get it to load the right modules. 09:32:38 so I got debian instead and its behaved a lot like freebsd :D 09:32:42 i dare to allege that there's more room for poesie in forth than in (many/most) other languages 09:33:12 Speuler: the way I see it, you can write poetry in forth if you know what you are doing. 09:33:22 it will be odd, as it will only talk to the machine though. 09:33:35 the "knowing what you're doing" is important indeed 09:33:39 hehehe. 09:33:54 but how to know what one is doing is a difficult thing. 09:34:35 forth is a preprogramming language. you have to do a lot of things that other languages do easily. 09:34:37 it frees you from the terror of being supervised by the language 09:34:40 so not only do you write a language on top of it, you must know how to write that as well. 09:35:08 people can be happy about that 09:35:10 i am 09:35:33 Speuler: ever seen/heard of oz/mozart ? 09:35:38 gives me the feeling that i get a better view on the whole 09:35:57 nope, not that i recall 09:36:42 lemme see 09:36:44 uno momento. 09:36:47 you might like this :D 09:36:58 forth programmers don't tend to be locked into a single layer of the process of creation of machine-executable instruction sequences 09:37:10 but encorporate many of them 09:37:22 from the hardware up to the top app level 09:37:48 speuler take a look at this: http://www.mozart-oz.org/documentation/tutorial/node1.html#label2 09:37:50 they require a language which as as flexible as they are 09:38:45 in turn does forth give you access to those other layers, enabling them to easier learn about them 09:39:01 Hmm. Opera crashed AGAIN. 09:39:14 Robert: it is time to write a browser in forth :D 09:39:21 Speuler: did you see? 09:39:25 :) 09:39:33 that's probably why many forth programmers feel comfortable with asm 09:39:51 but don't find it sufficient to address all their requirements 09:40:04 yes looking at 09:40:56 looks nicely minimal 09:41:14 but not obfuscated 09:41:24 yes. they wrote a whole text book to go with it as well. 09:41:31 they call it the 'kernel based approach'. 09:41:39 sounds too much like someones favorite language. 09:41:55 ai oriented 09:42:30 a little 09:42:52 The book's scientific foundation is the kernel language approach. In this approach, practical programming languages are defined by translating them to kernel languages that contain a small number of programmer-significant concepts. 09:42:56 unquote 09:43:31 http://www.info.ucl.ac.be/people/PVR/book.html 09:43:52 emacs as frontend ... 09:43:56 bad bad. 09:44:00 "If you are not familiar with Emacs or its terminology, you should consult the Emacs on-line tutorial" :) 09:44:06 hahahah 09:44:32 Speuler: I think the authors might have learnt forth. what do you think? 09:44:47 looks like worth to have a look at 09:45:40 the book is missing a language though. 09:45:44 ;) 09:45:56 on the Practical Application of Prolog and the Forth International Conference on ... In 09:45:57 Gert Smolka, editor, Proceedings of the Third International Conferenc 09:46:12 ert Smolka. ... Elf Forth is a high-performance Forth compiler 09:46:37 project PROTOS (Christoph Beierle, 09:46:38 Gert Smolka). ... Exposure to: assembler (Z80, 6800, 68000), Forth, 09:47:02 looks like the developers DID learn forth 09:47:08 hehehe 09:49:32 when I am done reading this 'other' book, I shall read the oz/mozart book next. 09:50:15 Seif Haridi, and Per Brand : "...small devices. They are typically programmed in a low-level language (e.g. FORTH), often unconnected and with no way to upgrade the software. The capabilities of the basic..." 09:53:39 oz/mozart is apt-getable. 09:53:53 oh ? 09:53:59 ja 09:54:15 --- quit: I440r (Read error: 60 (Operation timed out)) 09:54:24 http://www.mozart-oz.org/download/view.cgi?action=debian 09:54:54 got indeed two mozert packages in main/devel 09:54:55 zart 09:55:05 3 09:55:13 docs too 09:55:14 :) zart (zárt) is closed in hungarian 09:55:28 s/zert/zart/ :) 09:55:42 and it insists on opening emacs. 09:55:54 Mozart Compiler 1.2.5 (20030205) playing Oz 3 09:56:31 how about speed ? 09:56:39 7 meg ?? 09:56:43 I dunno how to make it run :D 09:56:52 I don't know the language at all! 09:57:08 I found the book's reference in some newsgroup and took a look at it. 09:57:14 and I thought it smacked of forth. 09:57:23 good thing to mention it here 09:57:33 sounds like forth, smells like forth, ISforth :D 09:57:43 * Speuler won't bash gilb for being OT 09:58:35 thank you most gracious kind sir for not bashing me. 09:59:01 may the ancestors smile upon you. 09:59:07 and may you live to see several mango seasons! 09:59:33 oh 09:59:39 gilbertDEB 10:00:59 1,2,4 here 10:01:01 1.2.4 10:01:27 (20020911) 10:01:47 not frequently updated 10:03:10 the version? 10:03:36 To get access to the repository, add this line to your /etc/apt/sources.list and run apt-get update to update your local package database. 10:03:42 you might have missed that. 10:04:04 --- join: I440r (~mark4@ip209-183-83-35.ts.indy.net) joined #forth 10:57:16 --- quit: gilbertdeb ("Client Exiting") 11:07:05 http://freshmeat.net/project-stats/view/28699/ 11:10:01 * Speuler wonders whether he should put bashforth on sourcefourge :) 11:18:13 --- join: I440r_ (~mark4@ip209-183-83-104.ts.indy.net) joined #forth 11:26:15 --- quit: I440r (Connection timed out) 12:45:04 --- join: gilbertdeb (~gilbert@fl-nked-ubr2-c3a-29.dad.adelphia.net) joined #forth 12:45:57 --- join: Kitanin (~clark@SCF61185.ab.hsia.telus.net) joined #forth 12:46:47 Speuler: ? 12:59:16 --- quit: Speuler (Read error: 110 (Connection timed out)) 13:00:26 --- join: Speuler (~Speuler@mnch-d9ba4bdd.pool.mediaWays.net) joined #forth 13:05:26 --- quit: Kitanin (Read error: 104 (Connection reset by peer)) 13:07:20 --- join: Kitanin (~clark@SCF61185.ab.hsia.telus.net) joined #forth 13:23:55 --- part: gilbertdeb left #forth 13:29:32 --- join: deluxe (~deluxe@pD950FE23.dip.t-dialin.net) joined #forth 13:29:36 --- join: gilbertdeb (~gilbert@fl-nked-ubr2-c3a-29.dad.adelphia.net) joined #forth 13:29:38 salut 13:29:46 salut. 13:29:52 ca va? 13:30:20 no more bsd? ;-) 13:30:33 heheh 13:30:35 debian rules. 13:30:42 have you seen bashforth? 13:30:53 where? 13:31:02 * deluxe curious 13:31:04 logilan.info/~l/ 13:31:11 http://logilan.info/~l/ 13:31:34 it was created by speuler. 13:43:55 --- part: gilbertdeb left #forth 13:58:06 deluxe: don't bother with v0.01 - that's for historical reasons 13:58:19 :-) 13:58:25 deluxe: radix has been updated too 13:59:26 of both last version is recommended. 0.35 for bashforth, 0.03 i think for radix 14:03:57 Speuler: what are (highest) goals for bashforth? 14:04:06 has been redefined now 14:04:31 now its becoming the template forth for a target translator 14:04:40 before it was fun 14:04:59 Speuler: target? 14:05:02 intend to target avr source and javascript first 14:05:04 avr asm 14:05:39 small microcontroller and unlikely script language :) 14:05:58 that should give me the two extremes 14:06:36 Speuler: what are you doing on avr? 14:06:42 nothing. 14:06:51 just picked it because i got an emulator 14:07:11 Speuler: building robots ;-) 14:07:24 know pic, so avr shouldn't be such a big step 14:08:36 Speuler: (still trying to remember the other well-known name for avr chips) 14:09:08 should i get it to translate to these two, other langs fall somewhere between these 14:09:24 Speuler: i know they have evaluation boards 14:09:45 yes. cheap controller too. but emulator will do here 14:10:16 can still put it on an avr if i like or need 14:10:25 or robert can test it for me 14:12:50 Speuler: good to hear about bashforth :-) 14:13:33 no commercial potential 14:14:19 one of the few uses i'd see for it the way it is, is educational 14:14:45 or, reducing the threshold for people who want to have a quick look at forth 14:14:51 without actually installing anything 14:15:29 it is quite forth-alike. with create does> , catch throw and shit 14:15:42 Speuler: btw ever tried forth evaluation boards? 14:16:00 novix, psc1000 14:17:17 got it from where? 14:17:28 wanted to get a i21 board but ws difficult to come by, by telephone order 14:17:41 novix: pijnenburg 14:17:50 psc: from the maker 14:18:02 ic 14:18:11 why difficult? 14:18:12 i21: ting 14:18:21 i don't speak chinese 14:18:28 :-) 14:20:53 he. you're not far 14:20:56 10 hops 14:21:30 first 5 on my side 14:22:04 bayern ? 14:23:28 send ting an email that you want to communicate (the order) here on irc ;-) 14:23:29 freiburg is already 11...13 hops 14:24:25 was about 5 years ago that i had interest 14:24:34 tried thrice 14:25:30 maybe i may get intested in the x25 14:27:11 do they say "grias di" where you come from ? 14:28:03 no, but i heard that b4, know what it means 14:28:57 8th hop is already orbit ;-) 14:30:09 helau or alaaf ? 14:30:54 * deluxe definitely is interested in x25, but whoelse is? 14:31:13 does it matter ? 14:31:45 to be or not to be, x25 14:31:48 no? 14:31:54 think so 14:32:34 does it matter ? <-- yes 14:32:47 think so 14:33:25 we don't need to be lemmings following the crowd 14:33:48 context? 14:33:55 we wouldn't be here if we would be 14:34:34 no flames at all here 14:34:41 context: definitely is interested in x25, but whoelse is? does it matter ? <-- yes 14:35:02 no flames ?? 14:35:07 don't arouse the dragon 14:35:12 :) 14:35:17 ok :-) 14:35:42 it's a home place ;-) 14:36:28 there a a lot of friendly channels, i note 14:36:50 the bigger, the harsher the climate 14:37:31 Speuler: okok :) 14:40:27 Speuler: what about your new hp? 14:40:50 even a channel, about 50 people, everyone root 14:41:13 ? 14:41:16 sometimes a nuisance comes in, starting to mass deop 14:41:31 root = op 14:42:32 but that's dealt with all right 14:43:28 i'm out for a while 14:43:41 cu 14:43:52 later 14:45:26 --- part: deluxe left #forth 15:11:28 --- join: karingo (karingo@59.portland-01-02rs.or.dial-access.att.net) joined #forth 15:17:03 hi 15:26:45 --- quit: Kitanin ("Client killed by developer sick of answering stupid questions.") 15:41:36 --- join: kapple (karingo@246.portland-11-12rs.or.dial-access.att.net) joined #forth 15:43:20 --- join: k (karingo@33.portland-01rh16rt.or.dial-access.att.net) joined #forth 15:46:22 --- quit: k (Client Quit) 15:49:45 --- quit: karingo (Read error: 60 (Operation timed out)) 15:51:54 --- join: karingo (karingo@33.portland-01rh16rt.or.dial-access.att.net) joined #forth 16:03:56 --- quit: kapple (Read error: 113 (No route to host)) 16:14:47 --- quit: Fractal (Read error: 110 (Connection timed out)) 16:19:55 --- quit: karingo () 16:44:50 --- quit: I440r_ (Excess Flood) 16:45:12 --- join: I440r_ (~mark4@ip209-183-83-104.ts.indy.net) joined #forth 16:45:28 back 16:45:40 :) 16:47:47 /nick i440r 16:48:26 hee 16:50:01 hee too 16:50:22 what's up 16:50:30 hmm 16:50:33 * Speuler checks 16:50:37 stars, clouds 16:50:52 a few planets 16:51:55 know marvin from hitchhikers' guide to the galaxy ? 16:51:56 What about Lucipher? 16:52:03 Yes, I like him. 16:52:08