00:00:00 --- log: started forth/05.07.08 02:36:02 --- join: arke (f2@bespin.org) joined #forth 04:54:40 --- join: swalters (~swalters@2416457hfc118.tampabay.res.rr.com) joined #forth 05:43:15 --- nick: Raystm2 -> nanstm 06:39:01 --- join: PoppaVic (~pete@0-1pool46-235.nas30.chicago4.il.us.da.qwest.net) joined #forth 06:39:23 Mornin' 06:40:03 Hi 06:40:26 WHat's shakin' this AM? 06:41:17 Not much, really, justh woke up. 06:43:46 Dittos... Trying to put together a pile of variation notes. 07:00:13 --- join: sproingie (foobar@64-121-15-14.c3-0.sfrn-ubr8.sfrn.ca.cable.rcn.com) joined #forth 07:00:23 lo 07:00:41 mornin 07:06:29 Di 07:07:07 hmm... For some strange reason I'm thinking I can write colon/next and such as hi-level words.. Interesting. 07:08:34 starting forth gives forth definitions for colon and semicolon 07:10:03 next might be a bit tougher. i suppose forth can be metacircular. bit painful tho 07:10:09 yeah... THis is my conceptual libtil c/forthish interface 07:10:48 next is really just an implementation trick. you never see it in forth itself 07:11:19 yeah. Alas, leaving the stackframe and calls to act for Rstack and such will necessitate some voodoo 07:12:17 * sproingie is working on some utf8 words for retroforth, crc's doing floating point 07:12:48 utf8 would be interesting, should be a fully transparent install, to my mind 07:13:09 maybe i'll take a look at the garbage collector and try that out 07:13:55 yah, rf has no problems with utf8 data in strings, you just have to lose the assumption that the length is the number of chars 07:16:21 well, char-width as well 07:16:30 Same sorta' issue plagues C 07:16:52 forth has no "char" type as far as i'm concerned. i just consider c@ and company to be poorly named 07:17:14 I generally agree, but it's what they left behind 07:17:49 especially considering forth's single implementation defined type, the "cell". you'd think chuck would have picked a word that wasn't ambiguous with "cell" 07:17:49 hmm.. Glad I downloaded gforth (I thought I had before)... I see the FFI stuff tathi mentioned. 07:17:51 like "byte" 07:18:24 It's not a prob if that ABI is clearly defined and accessible 07:21:28 alas, the ABI is pretty painful and ugly to learn about 07:23:44 abi for what? 07:24:12 oh, uint8_t/byte, char, int, cell, word, dword, etc 07:24:42 It's just not pretty, and it it's all non-intuitive to boot 07:24:57 well some of those are machine types, some are implementation-defined types 07:25:16 i think we can safely assume that bytes are octets now 07:25:26 I think of them collectively as the ABI - since they interface in several fashions 07:25:33 some machines actually did have bytes that weren't 8 bits 07:25:40 I always hated that 'octet' term, but I'm an antique 07:26:06 sure, pretty rare birds today.. And 4 bits was a "nybble" 07:26:45 you'll still see nybbles referred to when you deal with device drivers 07:26:57 as you should 'bytes' 07:27:22 the probs start around 'char' 07:27:52 well in C, it's a machine type, always a byte 07:28:01 in modern languages, it's an abstract type 07:28:07 yeppers 07:29:32 c did abstract char some ... never specified whether it was signed or unsigned 07:29:59 perfectly idiotic "decision", really 07:30:10 or more like lack of one 07:30:10 I believe they settled on default (some std) being 'sighned' - because there is a flag to force them usigned default 07:30:24 no i think it's still implementation-defined 07:30:30 but, it's messy. 07:30:52 unsigned makes more sense. ascii is unsigned, you don't see any negative ascii chars 07:31:02 right 07:31:26 I see the pt, but K&R had one idea, and the commies went from there 07:32:38 I can't much appreciate committees/commies that dictate syntax/semantics, ignore libc, and then don't even publish a std .l/.y pair - for the preprocessor OR compiler. 07:32:47 i think by the time they got it to ANSI, the differences were too entrenched, so they just bailed on the signed/unsigned issue 07:33:15 ansi dealt with libc stuff quite definitively, they published a whole system spec 07:33:18 well, we have gnu, we have doze, we have ansi, and then ISO stuck it's stupid nose into it. 07:33:26 personally i think they should have ignored the system spec 07:33:46 ansi is crippled, however - they ignore a lot filesystem stuff, iirc 07:33:47 iso did hardly anything to ansi c 07:34:00 i dont think they ignore enough, frankly 07:34:07 it should have been a separate standard 07:34:20 well, it's ISO that makes people excited.. I think they are definitely on my shitlist 07:34:21 throw it to IEEE POSIX 07:34:44 heh - which posix? even that has several stds, and libc supports bits form them 07:34:48 IEEE should have gotten the system interface, all that fopen(), strlen() crap 07:34:59 and leave ANSI and ISO to the language 07:35:24 i think ANSI C came around long before IEEE POSIX did tho 07:35:35 well, I love C - but I also have a lot of feeling for forthish.. I definitely want a reconciliation. 07:35:44 the only standards before then were implementations 07:36:14 I figure it out the other day, though.. I can see why we are in such pain. 07:36:19 i wouldn't let DPANS's antics color your perceptions of standards bodies 07:36:19 figureD 07:36:48 oh, hell DPANS ;-) I forgot them.. No, I just watch the daily std-shit in ##C for pain 07:37:35 eh, #C is full of petty quibblers. the standard is pretty sane 07:37:53 which? 07:38:01 there's only one C 07:38:22 there's now only one unix: SUS 07:38:25 For myself, I let gnu run default; when I must I suffer ansi or posix shit 07:38:31 SUS is merely the new name for POSIX 07:39:08 the language is over 30 years old... They still can't codify it decently - and that means semantics, syntax and libc 07:39:40 The problems - I believe - stem from a complete refusal to recognize what it was intended to do. 07:40:01 before POSIX, there was System V (aka SVID), 3.2 BSD, and some godawful acronym out of X/Open I can't even remember 07:40:08 ..it was designed to act as a super-assembler. THat's all. 07:40:09 it was a lot worse 07:40:33 no it wasn't, it was designed to be a portable system writing language. it succeeded admirably 07:40:35 Nowadays, I think the issue is the platform-portability 07:41:13 well yes, systemic-language I'll buy - I've still K&R v1 around. 07:41:27 eh, at least get the ansi C version 07:41:53 nah, mine brings up fond memories of days before goddamned autoshit and doze 07:42:28 I wish I had a really good doc on generating .o and the linker/loader.. 07:42:41 autotools are the crap. autoconf isn't so bad, automake is the worst thing to happen to make since the TAB char 07:42:51 I think our weak-point is not just the platforms, but the assembler. 07:43:47 what's the matter with the assemblers? 07:43:48 sproingie: the prob with autoshit is just that - it's a royal mess and whore.. Not only ugly and inconsistent, but requiring the goodwill of at least 2 diff programs that may not be portable. 07:44:12 autotools require bunches and bunches of external tools 07:44:21 makes it not run at all on windows 07:44:21 I'd like to see a Portable Assembler - and let folks plug in modules to generate actual code. 07:44:40 sure, they call it C ;) 07:44:51 nope - C is a notch too high 07:44:54 seriously tho, C actually has too much policy 07:45:14 you mean the committees/groups/std? 07:45:14 but there's some work going on around that lately 07:45:24 no, runtime policy 07:45:34 I'm lost.. 07:45:36 like dictating particular calling conventions or symbol naming 07:45:41 ahhhhh 07:45:43 ok 07:45:44 stack cleanup order 07:45:45 Yes 07:45:47 that sort of thing 07:46:11 I spoke the other day with tathi, and - you know? - there seems to be NO stack-frame lib. 07:46:11 C-- is like a C without the policy. and it does have, for lack of a better word, a "plug-in" type system for putting in policy 07:46:39 there's also MLRISC and LLVM 07:46:52 LLVM can be interpreted or compiled 07:46:58 It's almost too late for C.. I could handle a similar goal and semantics, but they've about abused it as far as they can 07:47:08 what is "LLVM"? 07:47:14 low level virtual machine 07:47:21 jfgi 07:47:29 url? 07:47:57 google knows everything: http://llvm.cs.uiuc.edu/&e=9833 07:48:12 yes, the "portable assembler" I suggested would work against a "virtual processor" 07:48:31 you're talking about any virtual machine then 07:48:55 LLVM is pretty far along as VM's go 07:49:00 cool 07:49:08 maybe that will suffice.. Will look it over 07:49:16 and they even have a forthlike language for it ;) 07:50:00 excellent 07:50:58 good way to learn about compiler concepts like SSA too 07:51:16 It'd be a huge milestne if I gave up on C for it ;-) 07:51:26 well it's written in C++ 07:51:43 ewww - gag me 07:52:08 eh. unless you're adding something to the compiler itself, you don't need to mess with the C++ 07:52:12 They can't metacompile, wh? ;-) 07:52:27 very true 07:52:44 i dont think they have a C++ front-end for it yet 07:53:01 Thank the Lord 07:53:19 actually it can backend gcc, so in that way it does have front-end 07:53:29 Damn it, what the fuck are these files? 07:53:43 well one of their aims is to produce a full blown real compiler, an alternative to gcc 07:53:47 I have 4 supposed disk images, using file(1) just gives me a blank line. 07:54:02 tho now that gcc4 came out with its own SSA backend, that might have stolen a lot of llvm's thunder 07:54:08 so it might never achieve that goal now 07:55:01 i guarantee that llvm is better-documented than gcc's internals tho 07:55:07 SSA? 07:55:12 static single assignment 07:55:18 there's a great wikipedia article on it 07:55:40 Hmm... No idea what it means.. I never did a degree in CS/CE 07:55:46 forth is fairly close to being SSA if you think of "dup" as creating a new variable 07:55:53 I'll check it when the 3 DL are done 07:56:07 http://en.wikipedia.org/wiki/Static_single_assignment_form 07:56:09 ahhha 07:56:26 loading 07:56:37 not quite SSA with forth tho .. for one it's not static, whereas SSA of course is 07:56:57 forth is linear combinators (at least according to one writeup) 07:57:37 yeah, the ivory-tower folks "say" all sortsa' things 07:58:34 Sometimes they make sense... Sometimes they spew vomitus to further their careers 07:59:03 eh, the paper i'm referring to was all code and no greek 07:59:27 mostly lisp code, tho you could tell he was basically writing forth in lisp 07:59:37 well, eventually it'll load past the 3 dl's I'm running;-) 07:59:54 * sproingie thinks most people usually do the reverse, write some kind of lisp in forth 07:59:58 crap.. lisp.. argh 08:00:15 forth and lisp have a lot in common actually 08:00:28 lisp makes my eyes bleed - nearly like C++ 08:00:29 so why did somebody used it for a game engine? 08:00:49 PoppaVic: you gotta open that mind of yours a bit more 08:01:10 dude, 20 years ago it was 08:01:16 ah, C++ isn't painfull, when you don't use its oop features much. 08:01:22 just ignore the NASTY-LONG-BUREAUCRATIC-IDENTIFIERS of common lisp 08:01:26 CL is like ANS forth 08:01:28 nowadays, I just stick to what works well 08:01:32 there's still a good language under all that crud 08:01:41 virl: I didn't mean FOR me, I meant to read others whacked hacks 08:02:34 define: 'whacked hacks' I don't read much of source of foreign people, because I can't read it ;-) 08:02:43 There must be a secret club in C++ circles, where you can't use a ptr or a struct in a struct or even a ptr in a struct - instead: you polymorph and inherit and hide 08:02:43 anyway, forth and lisp both have macro systems that embeds a fully functioning runtime interpreter into the compiler 08:03:28 yep, understood: lisp slightly predates forth - same universe, different paths 08:03:43 i see pointers inside structs all the damn time in C++ 08:03:50 maybe you need to read more real code 08:04:43 actually nesting struct instances creates bloatsome messes, so it's not usually done except in trivial cases 08:04:45 Could be.. and could be I've read too much - Chill and smooth the hackles, sproingie ;-) 08:05:35 PoppaVic, when this C++ Code is a pain for you, then you want to kill the people who made Java ;-) 08:05:46 Suffice to say, C++ had a few "features" I liked, and I tried it long, long ago. But C gets used more and is easier on the eyes 08:05:47 C++ took a while to mature, since it came out into the mainstream before most implementations had templates 08:06:00 virl: nahh, I just ignore java 08:06:17 i'd say templates are C++'s best feature (if not its best syntax), and classes are just gravy 08:06:28 trust me, AT&T was around.. and it's still loathsome 08:06:39 stroustrup would probably disagree, but eh 08:06:40 I can't I have a friend who code in java, and its painfull and very ugly. 08:06:46 templates were an interesting idea, most assuredly 08:06:49 i think we all agree on that 08:06:58 * sproingie er that was to virl 08:07:18 even slava of jedit fame has given up on java in disgust 08:08:54 the same for C# wha, how can somebody design such a disgusting language! it is more disgusting than java. 08:09:07 I've been trying to slowly compile new ideas.. 08:09:22 i think bjarne stroustrup has lost it. he's pushing for a standard GUI lib for C++, and apparently his only problem with template syntax is that foo> requires a space between the >> 08:09:34 I still like the L->R word/by/word forth-interp 08:10:28 I will never learn to enjoy using yacc/bison 08:10:50 yacc and bison are ancient. there's far better compiler generators out there 08:10:59 What I was considering is how to best enable words to do some of their own lexing. 08:11:45 there are "better" everything.. Doesn't mean systems install them - and often "better" means "because says so" 08:12:02 so what, my system didn't come with bison 08:12:15 sure 08:12:18 didn't stop me from getting lemon and antlr 08:12:37 * sproingie has actually heard many bad things about antlr, but others swear by it 08:12:49 it's an option. Many programs are.. Ahh, the Z school. Except the latter is C++, is it not? 08:13:16 in my book, "better" means "didn't feel like performing oral surgery on myself without anesthetic" 08:13:24 yes, I've heard MANY thinks about multiple programs.. We end up in the same boats in the end. 08:13:59 anyway, forth hardly requires a static parser. lisp neither 08:14:02 sproingie: I don't fault using a tool you understand. Go for it. 08:14:12 smalltalk is also in a camp that doesn't care much for compiler generators 08:14:13 exactly 08:15:02 smalltalk was originally parsed much like forth: strictly left to right, with some words consuming extra words before going back to the top level stream consumer 08:15:18 I'm trying to puzzle out a way to decently allow for a dynamic lexer as well as a dynamic parser. Generating dynamic code. 08:15:29 nowadays it's a little more traditional, parses whole statements at a time, up to the trailing . 08:15:34 yes, I can almost recall smalltalk 08:15:50 isn't forth an ideal framework for a dyamic lexer/parser? 08:16:02 yeppers 08:16:11 if you want the LL(k) parsing bits, you can try grey 08:16:14 comes with gforth 08:16:16 Which is why I am working on this libTIL thing 08:16:36 I'll have to look for it 08:16:56 might be gray. i always spell it with a 'g' 08:17:06 er with an 'e' 08:17:11 I think the worst prob is an entire net of interest and issues, and mostly a lack of interest 08:17:12 * sproingie thinks most people spell grey with a g 08:17:28 yes, I know some folks argue the 'e' and 'a' 08:17:36 PoppaVic: heh, welcome to my world 08:17:50 * sproingie has noodled away the morning on irc instead of working on his utf8 words 08:18:11 heh - dude, I was there years before.. I try not to taint folks too much 08:18:35 it's just such tedious low-level bit-banging, i guess i have to force myself to work on it 08:18:49 sproingie: just a lexicon? Or making it a selectively-default modal-lexicon? 08:19:31 just a lexicon. anyone who wants to integrate it further is free to write words on top of it 08:20:03 cool.. Just curious - parallels normal chars/strings then, I presume? 08:20:05 ultimately a unicode string that can pull in the unicode symbol dictionary would be a nice thing 08:20:14 u" hello world\u{INTERROBANG}" 08:20:29 ahh 08:20:30 i think i'll stick to \uxxxx in the meantime 08:20:58 prolly not a bad choice. 08:21:24 java doesn't support named unicode chars either. perl and python both do tho 08:21:50 names vary though, do they not? 08:21:55 the unicode named character dictionary is huge 08:22:12 nope. unicode has standard names for every char 08:22:17 yep, aware of it 08:22:20 all in uppercase ascii in english 08:22:31 ahhh 08:22:46 so, it's one-off for all dialects universally 08:23:28 interesting - and how would you execute a 'macro' amid a string-input? 08:23:50 dialects are more a spoken word thing. the character names are more metadata, the only thing most implementations have to support are the numbers 08:24:08 yeppers 08:24:47 there's work going on on unifying all the han characters into a single plane, but i doubt that'll ever happen to everyone's satisfaction 08:24:54 yer looking at some sorta' infix-parsing solution, then 08:25:19 yeah, I can't help asia. It's worse than the world accepting ascii 08:27:39 well, unicode's my way of helping asia. even if they'd rather use big5 or euc 08:27:59 heh 08:28:21 yer just too kind, sproingie ;-) 08:28:45 * sproingie doesn't see retroforth becoming an international sensation to where people will be demanding every encoding under the sun 08:29:15 Sure they will, it's the nature of the anti-ascii universe 08:30:38 * sproingie has more damn problems displaying hebrew and arabic on linux than on windows, amazingly 08:31:29 but hey, it does a bangup job selecting the right font for hindi 08:31:29 nahh.. remember: as an OS, Doze is a great graphics-engine ;-) 08:31:31 * sproingie snorts 08:31:45 i have the fonts, it just fails to select them most of the time 08:31:49 heh - Like I was worried ;-) 08:32:25 so it'll pick a font to render runic just fine, but i'm just SOL when it comes to hebrew i guess 08:32:38 Once Upon A Time, I felt the fonts/locale and shit was all pretty interesting.. Then I screamed and ran away 08:32:51 * sproingie just gets the little "unknown unicode char" box in firefox 08:33:05 but if i copy and paste it into a terminal, then lo and behold, hebrew 08:33:39 what's firefox's brain damage that it can't properly select a font? 08:33:40 sounds like window-updating 08:33:56 no, it's failing to select a font with hebrew in it 08:33:59 I've never used it 08:34:07 --- quit: virl (Read error: 104 (Connection reset by peer)) 08:34:08 not that i can read it, but it's nice to properly display it 08:34:11 I live in safari and call mozilla for editing 08:34:23 --- join: virl (icechat5@chello062178085149.1.12.vie.surfer.at) joined #forth 08:34:36 heh you probably have no problems with fonts on OSX 08:34:49 You might want to ask in C, or Zhivago 08:35:02 go to aljazeera.net and tell me if it renders for you 08:35:13 for me, it's a soup of boxes 08:35:30 true.. I use ascii 90% of the time, and xchat suffers me well, although occasionally I kick it 08:35:32 on windows, it renders perfectly 08:35:59 http://aljazeera.net ? 08:36:16 maybe www.ajazeera.net 08:36:18 stupid net name 08:36:22 should be arabic 08:36:31 er www.aljazeera.net 08:36:35 goddam keyboard drops keys 08:37:08 oh here's the kicker. firefox renders the TITLEBAR in arabic just fine 08:37:21 which is not firefox's job actually, it's kde's 08:38:35 hmm, I think my code has a logic-fuckup.. shitwads 08:38:43 so firefox is basically failing to select proper fonts 08:39:01 still loading 08:39:12 and it's just ff on linux, so i suspect Xft is what's broken 08:39:18 I can't use a direct func-ptr 08:39:35 or more likely a gnome bug, i suspect this is higher-level than Xft 08:39:49 OK, renders fine - it's all arabic-gibberish. 08:39:59 oh yeah 08:40:05 renders perfectly in konqueror 08:40:09 stupid gnome piece of shit 08:40:14 yeppers 08:40:30 I told you: it's the engine/update 08:40:30 yeppers 08:41:20 if i can find adblock for konqueror, i'll never go back to ff 08:42:00 I liked mozilla before, and suffer safari now 08:42:39 safari had no probs, so - something is wrong in the engine or windows or rendering 08:42:51 well, safari's based on konq 08:43:11 i'd say the problem is with one of firefox's engines 08:43:34 anyway, gotta get going and get to work 08:43:37 * sproingie waves 08:43:43 * sproingie & 08:46:18 tootle, sprong 08:54:12 STATE is pissing me off. 09:31:13 hmm.. I think I see "an issue".. now, how to resolve it. 09:47:31 --- quit: PoppaVic ("Pulls the pin...") 10:02:51 --- join: JasonWoof (~jason@Herkamire.student.supporter.pdpc) joined #forth 10:02:51 --- mode: ChanServ set +o JasonWoof 12:28:52 --- quit: virl (Read error: 104 (Connection reset by peer)) 12:29:12 --- join: virl (icechat5@chello062178085149.1.12.vie.surfer.at) joined #forth 13:13:23 --- join: tathi (~josh@tathi.bronze.supporter.pdpc) joined #forth 13:26:23 --- quit: danniken ("Connection reset by queers") 13:43:37 --- nick: nanstm -> tiff 14:14:04 --- nick: tiff -> nanstm 14:35:37 --- join: qFox (~C00K13S@92pc222.sshunet.nl) joined #forth 14:35:38 --- quit: qFox (Remote closed the connection) 14:35:41 --- nick: nanstm -> TIFF 14:36:11 --- nick: TIFF -> tiff 15:27:53 --- nick: tiff -> vickey 15:30:41 --- nick: vickey -> tiff 15:45:09 --- quit: saon (Read error: 110 (Connection timed out)) 15:45:15 --- join: saon|smg1 (~saon@c-66-177-224-222.hsd1.fl.comcast.net) joined #forth 15:45:19 --- quit: saon|smgl (Read error: 110 (Connection timed out)) 15:47:01 --- join: saon (1000@c-66-177-224-222.hsd1.fl.comcast.net) joined #forth 17:31:29 --- quit: Robert ("FORTHKANA") 18:15:45 --- quit: virl (brown.freenode.net irc.freenode.net) 18:15:45 --- quit: swalters (brown.freenode.net irc.freenode.net) 18:15:45 --- quit: madwork (brown.freenode.net irc.freenode.net) 18:15:46 --- quit: ianp (brown.freenode.net irc.freenode.net) 18:15:46 --- quit: madgarden (brown.freenode.net irc.freenode.net) 18:15:47 --- quit: JasonWoof (brown.freenode.net irc.freenode.net) 18:15:47 --- quit: Snoopy42 (brown.freenode.net irc.freenode.net) 18:15:47 --- quit: skylan (brown.freenode.net irc.freenode.net) 18:15:47 --- quit: warpzero (brown.freenode.net irc.freenode.net) 18:15:49 --- quit: saon|smg1 (brown.freenode.net irc.freenode.net) 18:15:49 --- quit: tathi (brown.freenode.net irc.freenode.net) 18:15:49 --- quit: onetom (brown.freenode.net irc.freenode.net) 18:15:51 --- quit: ccfg (brown.freenode.net irc.freenode.net) 18:15:51 --- quit: sproingie (brown.freenode.net irc.freenode.net) 18:15:51 --- quit: arke (brown.freenode.net irc.freenode.net) 18:15:51 --- quit: tiff (brown.freenode.net irc.freenode.net) 18:15:53 --- quit: cmeme (brown.freenode.net irc.freenode.net) 18:15:53 --- quit: crc (brown.freenode.net irc.freenode.net) 18:29:57 --- join: JasonWoof (~jason@Herkamire.student.supporter.pdpc) joined #forth 18:29:57 --- join: saon|smg1 (~saon@c-66-177-224-222.hsd1.fl.comcast.net) joined #forth 18:29:57 --- join: virl (icechat5@chello062178085149.1.12.vie.surfer.at) joined #forth 18:29:57 --- join: sproingie (foobar@64-121-15-14.c3-0.sfrn-ubr8.sfrn.ca.cable.rcn.com) joined #forth 18:29:57 --- join: swalters (~swalters@2416457hfc118.tampabay.res.rr.com) joined #forth 18:29:57 --- join: arke (f2@bespin.org) joined #forth 18:29:57 --- join: Snoopy42 (snoopy_161@dsl-084-058-128-011.arcor-ip.net) joined #forth 18:29:57 --- join: tiff (~vircuser@adsl-68-95-253-95.dsl.rcsntx.swbell.net) joined #forth 18:29:57 --- join: madwork (~madgarden@derby.metrics.com) joined #forth 18:29:57 --- join: skylan (~sjh@dialup-216-211-4-39.tbaytel.net) joined #forth 18:29:57 --- join: crc (crc@pool-70-110-172-173.phil.east.verizon.net) joined #forth 18:29:57 --- join: cmeme (~cmeme@216.184.11.2) joined #forth 18:29:57 --- join: onetom (~tom@ns.dunasoft.com) joined #forth 18:29:57 --- join: warpzero (~warpzero@wza.us) joined #forth 18:29:57 --- join: ianp (~ian@inpuj.com) joined #forth 18:29:57 --- join: madgarden (~madgarden@Toronto-HSE-ppp3708567.sympatico.ca) joined #forth 18:29:57 --- join: ccfg (ccfg@dsl-roigw3de0.dial.inet.fi) joined #forth 18:29:57 --- mode: irc.freenode.net set +oo JasonWoof crc 19:24:55 --- quit: Snoopy42 (Read error: 131 (Connection reset by peer)) 19:25:35 --- join: Snoopy42 (snoopy_161@dsl-084-058-132-245.arcor-ip.net) joined #forth 19:49:16 --- join: danniken (CapStone@ppp-70-249-186-85.dsl.ltrkar.swbell.net) joined #forth 19:49:40 --- part: danniken left #forth 20:29:07 --- join: danniken (CapStone@ppp-70-249-186-85.dsl.ltrkar.swbell.net) joined #forth 20:32:15 --- join: LOOP-HOG (~chatzilla@sub22-119.member.dsl-only.net) joined #forth 20:32:19 hi 20:32:22 anybody home? 22:12:32 --- quit: LOOP-HOG ("ChatZilla 0.9.61 [Mozilla rv:1.7.1/20040707]") 22:54:29 --- quit: danniken () 23:04:01 --- quit: JasonWoof ("off to bed") 23:49:49 --- join: Sumerian (~Smirf@H66ae.h.strato-dslnet.de) joined #forth 23:51:28 --- part: Sumerian left #forth 23:59:59 --- log: ended forth/05.07.08