00:00:00 --- log: started forth/05.06.10 00:00:08 what are they called? 00:00:45 CNAMEs? 00:00:48 yeah 00:00:51 yah, they suck 00:01:04 I never even use them in my zone files 00:01:24 --- join: vitaminmoo (~vitaminmo@dsl-95-113.peak.org) joined #forth 00:01:27 I've never used them either, but they have caused problems at work 00:01:50 one customer had one on their dns server pointing to one of the domains we hosted 00:02:54 yah, there are all sorts of lame games you can play 00:04:10 well, have fun with your irc client 00:04:15 I'm getting very tired 00:04:20 thanks 00:04:21 later 00:04:37 later 00:04:40 --- quit: Herkamire ("off to bed") 00:17:03 --- join: ark1 (~arke@pool-71-109-104-243.lsanca.dsl-w.verizon.net) joined #forth 00:17:06 --- part: ark1 left #forth 00:42:11 --- quit: arke ("leaving") 00:44:17 --- join: arke (~arke@pool-71-109-104-243.lsanca.dsl-w.verizon.net) joined #forth 00:53:14 test 1 2 3 ... 00:53:16 alallaa 00:54:24 yoh 00:54:29 sup arke? 00:55:42 playing with Gaim instead of irssi for IRC 00:55:49 maybe I'll end up liking it better 00:55:51 :) 00:56:47 --- quit: LOOP-HOG ("ChatZilla 0.9.61 [Mozilla rv:1.7.1/20040707]") 02:17:06 --- join: Serg[ICQ] (~Miranda@212.34.52.140) joined #forth 02:44:46 --- quit: onetom_ (brown.freenode.net irc.freenode.net) 02:45:25 --- join: onetom_ (~tom@ns.dunasoft.com) joined #forth 02:48:02 --- quit: alexander_ ("Leaving") 03:55:49 --- join: nothingmuch (~nothingmu@yovalk.bb.netvision.net.il) joined #forth 03:55:56 hello 03:56:38 i'm trying to learn haskell, and as a toy project i'm trying to learn forth so I can implement a compiler 03:56:48 (how many times has that been said here before?) 03:57:26 so I was wondering about the lowest level semantics the host language must provide 03:57:33 specifically regarding branching 04:14:53 also 04:14:59 what control structures are hard to implement in forth based on primitives 04:15:23 and what is the state variable's nature? is state a word that points to an address, that you can write the state data to? 04:15:34 or is it something more "hard coded"? 04:35:16 is there a compilation time word that pushes the instruction pointer onto the stack? 04:39:15 --- quit: onetom_ (Read error: 54 (Connection reset by peer)) 04:39:23 --- join: onetom (~tom@ns.dunasoft.com) joined #forth 04:57:22 --- join: PoppaVic (~pete@0-2pool236-167.nas22.chicago4.il.us.da.qwest.net) joined #forth 04:58:05 Mornin' 05:01:01 good day 05:21:55 --- quit: Serg[ICQ] ("Miranda IM! Smaller, Faster, Easier. http://miranda-im.org") 05:23:14 --- quit: nothingmuch () 05:44:57 Dobry vecer! 06:04:23 --- join: nothingmuch (~nothingmu@CBL217-132-121-216.bb.netvision.net.il) joined #forth 06:24:11 --- join: nothingmuch_ (~nothingmu@yovalk.bb.netvision.net.il) joined #forth 06:25:05 morning 06:25:23 lo 06:25:35 --- quit: nothingmuch (Read error: 60 (Operation timed out)) 06:26:35 do you know of an illustration of the bare metal a forth machine must supply? 06:26:46 e.g. branching 06:27:14 heh.. I can't even find my f83 programmers manual 06:27:51 there are forth sites, certainly there are branching via forth colon-defs 06:28:25 background: i'm trying to learn haskell and forth, by implementing a compiler for the latter in the former 06:28:34 good luck 06:33:47 so now I'm trying to see what parts the haskell side will have to provide 06:33:48 --- nick: nothingmuch_ -> nothingmuch 06:33:48 --- quit: nothingmuch (Remote closed the connection) 06:37:16 --- join: nothingmuch (~nothingmu@yovalk.bb.netvision.net.il) joined #forth 06:37:17 --- quit: onetom (Read error: 54 (Connection reset by peer)) 06:38:06 =/ 06:38:18 my hands are blocking the wifi's antenna 06:51:38 --- join: danniken- (CapStone@ppp-70-249-186-85.dsl.ltrkar.swbell.net) joined #forth 07:00:16 --- quit: danniken (Read error: 145 (Connection timed out)) 07:00:59 --- nick: danniken- -> danniken 07:04:20 PoppaVic, F83 is my favorite. :) 07:04:36 Yeah, in the long-ago, she was nifty 07:04:46 anymore, I generally tinker w/i gforth 07:08:57 --- nick: nothingmuch -> someguy 07:09:06 --- nick: someguy -> nothingmuch 07:10:15 --- join: I440r_ (~mark4@216-110-82-203.gen.twtelecom.net) joined #forth 07:12:43 --- join: Herkamire (~jason@c-24-218-95-147.hsd1.ma.comcast.net) joined #forth 07:12:43 --- mode: ChanServ set +o Herkamire 07:29:02 why is : not defined more like << parse-word two_plus_two : [ 2 2 + ] LITERAL ; >>, as far as the user is concerned? does the switch to coimpilation state need to happen earlier for some reason? 07:29:43 I don't understand the question 07:30:01 well, the : word takes the next token and makes it into a word 07:30:05 yep 07:30:10 why doesn't it take the word name from the data stack instead? 07:30:12 starts compiling 07:30:26 it's a convenience and a convention 07:30:27 because the word isn't on the data stack 07:30:31 it's on the input stream 07:30:52 You COULD code like that, I suppose - before defining : 07:31:19 if you put the word before : then you'd have to quote it. 07:31:25 and why not "quote" it with : 07:31:31 right 07:31:34 " foo" : bar ; 07:31:40 is ugly and annoying to type 07:31:48 I was thinking of coding as ugly as using echo or cat 07:32:25 so does : taking a word off the input stream make it less flexible? or am I missing something? 07:32:30 The convenience of : is too high to suffer much of anything else 07:33:04 several words do parsing/look-ahead 07:33:35 It's part of Forth's language extension ability. 07:33:57 nothingmuch: it also has to do with trying to stay as RPN as possible 07:34:16 : FOO means less RPN than FOO : to mee 07:34:25 there have been modules that managed to deploy infix - but the code was just ugly 07:34:53 well, nothingmuch - you would be wrong.. I told you there were others 07:34:59 nothingmuch: you can't do FOO : because FOO would get compiled before it got to : 07:35:13 or, FOO would generate a word-not-found error 07:35:24 yeah, that was a silly example 07:35:46 which is more sensible: "10 constant decimal" or quoting 'decimal' to get to the stack, muck with the ten and then "constant"? 07:36:08 PoppaVic: please explain 07:36:22 PoppaVic: the former when a human is typing 07:36:24 under gforth, I type "see constant" 07:36:31 that is how it works, too 07:37:01 Remember, yer dealing with a language which is heavily RPN and mostly because it is stack-based 07:37:08 if you don't want a word parsed/executed/compiled as normal you have to put something before it. 07:37:29 you _have_ to, assuming you have a normal forth parser that just parses left-to right. no look-ahead 07:37:32 no "syntax" 07:37:37 right 07:38:02 no rewind, no backing-up... L->R input->stack 07:38:17 forth doesn't have an RPN parser. 07:38:24 it just ends up looking like RPN a lot of the time. 07:38:27 oh, well - I suppose there IS some "putback" ability 07:38:36 but it is not parsed as such, it just reads in one character/word at a time 07:38:48 then acts apon it before reading in more 07:38:48 sure, the math is almost always easiest to describe as RPN 07:39:13 data, data, op ... doodle, diddle 07:39:25 there are alternatives, but not with the normal forth way of reading input 07:39:31 eg, there's the colorforth method 07:39:42 iirc, that was nasty 07:39:46 put the word being defined in a unique color, and have no symbol at all 07:39:53 so suppose : is a word that is defined to be 'parse-word def-word', and def-word is defined as something like I asked about, is there a way to do it the other way? 07:40:10 nothingmuch: huh? 07:40:19 sure, you'd unfold it all - and it would be ugly shit 07:40:42 I'd recommend installing a forth with 'see' and friends.. Gforth is perfectly usable. 07:40:59 And, of course, the source is invaluable 07:41:06 PoppaVic: yes, i've been seeing gforth and minforth's ":", "constant", "create", etc 07:41:12 what is "unfold" in this context? 07:41:12 that's why i came here to ask =) 07:41:31 what 'see' does... what a sec, small paste in a sec... 07:41:45 see constant 07:41:45 : Constant 07:41:45 (Constant) , ; ok 07:41:45 see (constant) 07:41:45 : (Constant) 07:41:46 header reveal docon: cfa, ; ok 07:42:25 Herkamire: imagine ": : parse-word define-word-from-stack ; : define-word-from-stack ( just like : but from the stack instead of the input stream ) ;" 07:42:42 I peel into (unfold) constant, then (constant) - you want to mechanize this sorta' thing. 07:43:10 peel/peeR 07:43:24 i don't know what "peel" or "peeR" mean 07:43:41 peer-into look at scan read study examine 07:48:44 nothingmuch: yeah, that's how I'd implement it 07:49:09 nothingmuch: needs to switch to compile mode of course 07:49:20 Herkamire: so my question is what is the good reason for it not being this way? 07:49:31 because we have : ? 07:49:48 oh I get it 07:50:00 PoppaVic: he's not trying to change the usage pattern of : 07:50:06 just change the way it's factored 07:50:09 eg: 07:50:17 There is nothing that insists you NOT have such a word, nothingmuch 07:50:23 : : bl word $: ; 07:50:29 sure, I know he's refactoring 07:50:45 : $: add-to-dict COMPILE mode ! ; 07:50:49 Not sure what his goal or purpose is, though 07:51:06 you can still do: : foo bar ; 07:51:26 but you can also create words with $: with any string you can make 07:51:32 yep 07:51:38 this creates the possibility for cool stuff, like creating words that create 2 words 07:52:18 eg: 07:52:24 100 cells allot 07:52:29 oops 07:52:30 He needs to install something like gforth and do a lot of reading/tinkering 07:53:10 create foo 100 cells allot 07:53:10 cell-accessors foo 07:53:58 yep, done such many times 07:54:07 cell-accessors could create two words foo@ and foo! which would be equivelent to : foo@ cells foo + @ ; and : foo! cells foo + ! ; 07:54:33 I never could get into mucking with the details of gforth 07:54:41 could even create a voc/wordlist and allocate, then make voc current and all new defs specific to the allocated space 07:54:45 I had a hard enough time finding out how the basic features worked 07:54:53 I had a lot more fun writing my own 07:55:00 yeah, but then: I live in C 07:55:22 for me, c is getting very old 07:55:48 well, the alternatives don't do much for me 07:56:06 I'm old enough that C is fairly comfortable 07:56:59 Had the idiots at ANS and whatnot gotten serious long ago, and we'd had forth->.o and such, I'd have stuck with forth. 07:59:00 sorry, sister needed bike fudging 07:59:16 PoppaVic: i'm only asking because i'm curious, I don't want to actually achieve anything yet 07:59:27 well, that's how you would 07:59:29 I don't want forth pre-compiled 07:59:46 no, I wanted to incorporate working forth objects elsewhere ;-) 07:59:47 I really like being able to do things at compile time 08:00:07 I don't like objects 08:00:16 as I said, I live in C 08:00:18 Herkamire: I heard somewhere that forth people have a word for my kind 08:00:42 well, it's easy enough to write forths in C 08:01:01 nothingmuch: tinkerers? 08:01:10 as I said I'm learning haskell and forth together by trying to compile forth with haskell 08:01:13 hence the asking around 08:01:14 tinkerers? context please ;-) 08:01:24 oh, the word for people like me? 08:01:27 i have no idea 08:01:29 yeah 08:01:46 dunno if we have a word, just guessing 08:01:59 maybe you'd like this one? : foo bar ; 08:04:20 * nothingmuch is puzzled 08:05:52 --- join: sproingie (~chuck@64-121-15-14.c3-0.sfrn-ubr8.sfrn.ca.cable.rcn.com) joined #forth 08:12:30 newbie 08:13:09 yes, newbie 08:13:59 I can tell you, (from my ancient, rusty experience), that the best way to learn ABOUT forth is by getting the source, reading/compiling it and tinkering 08:14:23 * nothingmuch has just started to read minforth's C source, if that's what you mean 08:14:28 F83 was also a pretty nice "distro" 08:14:39 I dunno' minforth 08:14:47 http://home.arcor.de/a.s.kochenburger/minforth.html 08:15:08 chances are it's all in german, and that won't help me much ;-) 08:15:23 it's actually in english 08:15:31 german wouldn't have helped me either =) 08:15:32 the source as well? 08:16:10 yep 08:16:17 good deal 08:16:31 seems like a good impl to learn from 08:16:49 retroforth is also pretty good to learn from, proviso you aren't scared of asm 08:16:58 it's fairly readable for asm tho 08:17:07 sproingie: x86? 08:17:15 nothingmuch: yep 08:17:50 i'll have a look 08:17:55 i can read it, but I can't run it though 08:18:00 =/ 08:18:05 it's lavishly commented 08:18:13 There is a reason I use C ;-) 08:18:30 well retro has the advantage of being fairly simple 08:18:35 subroutine threaded 08:18:52 unfortunately, there are so damned many platforms and "standards" that the reason leaks a bit 08:18:53 but still laid out with a NEXT macro (in asm of course) 08:19:10 being subroutine-threaded, the NEXT macro is simply an alias for RET 08:19:49 There are pro & con for token-threading and subrot-threads 08:19:50 well retro conforms to no standard whatsoever, but for the most part lacks weird extensions 08:20:06 subr threading is smaller and simpler. rarely ever faster tho 08:20:18 small is rf's main goal 08:20:21 it should be faster and easier to debug as well 08:20:43 threading with tokens should be more portable and a trifle slower 08:21:05 in x86 assembler, are call/ret implemented with the stack that push/pop use? or is there a control flow stack as well? 08:21:29 same stack. i don't know what architectures have a separate data stack 08:21:47 many 08:21:56 return stack, though 08:22:10 oh, in ASM - no idea 08:22:14 forth needs 2 stacks 08:22:16 #TIBed for her pleasure... 08:22:16 data and return 08:22:26 nothingmuch: what architecture and OS do you have? 08:22:34 Herkamire: OSX/ppc 08:22:42 Herkamire: well, trying to live with one is interesting 08:22:51 ..and others also add a float-stack 08:23:12 nothingmuch: cool, you should try my forth. it's for ppc 08:23:28 Herkamire: sure 08:23:34 but I don't know PPC assembler ;-) 08:23:35 my osx port is still a little rusty, but... 08:23:37 it works 08:23:40 don't have to 08:23:54 nothingmuch: do you know the default dimentions of the osx terminal? 08:24:21 Herkamire: uhh, no clue... I think that's the first prefs setting I changed several years ago 08:24:40 and i've been lugging my prefs files since 08:24:58 nothingmuch: ah, you probably want herkforth 08:25:53 unless it only wants to run native ... wouldn't know, don't care to run pearpc 08:26:15 bochs is slow enough, i shudder to think of ppc emulation speed 08:26:26 wow! rf uses darcs! 08:26:33 nothingmuch: http://herkamire.com/jason/herkforth_for_mac_os_x 08:26:38 sproingie: RISC on CISC is easier than the reverse 08:27:05 nothingmuch: you sure? 08:27:12 nothingmuch: easier yes, faster no 08:27:20 I thought ppc emulated x86 faster than the other way around 08:27:26 ahh 08:27:33 cisc instructions aren't 1-1 with the clock, so they'll be damn pokey 08:28:05 actually, come to think of it, how are instructions like multiplications a 1 tick operation? 08:28:33 that might be an exception. or maybe they just have exceptionally zippy ALU's 08:29:11 what i can't get is how anything accessing mem could ever be 1-1 with the clock 08:29:13 nothingmuch: you have to do a couple little things (described on that page) to get herkforth adjusted to your terminal settings, but once you've done that it runs quite well under osx 08:29:19 well, minforth should interest him.. I dunno, looked odd to me. 08:29:41 or maybe i've just been fed an urban legend about risc, something that was true long ago but not now 08:30:05 most ppc instructions take one clock cycle. 08:30:08 not all though 08:30:22 shame chuck couldn't get the f23 mass produced 08:30:30 it sounded like it put the cell to shame for parallelization 08:30:38 sometimes certain instructions don't take any cycles 08:30:54 because of all those fancy features I forget the terms for 08:30:55 anybody know where crc's new documentation for learning retroforth is located? 08:31:02 branch-lookahead stuff 08:31:11 Herkamire: what's herkforth's original platform? aix? linuxppc? 08:31:27 nothingmuch: ppc linux 08:31:28 oh! I completely forgot I already have forth 08:31:33 OF =) 08:31:40 nothingmuch: heh :) 08:31:44 yah but it's hard to inspect sources in OF 08:31:59 i wonder how fun OF's is though 08:32:01 the UI ain't so hot tho 08:32:03 too bad apple is ditching it 08:32:15 maybe they'll use freebsd's bootloader 08:32:16 OF is good for poking around the device tree, and booting systems 08:32:20 that has bootforth 08:32:27 which is a stripped down FICL i believe 08:32:30 but I don't think you'll want to do much with it. there's no good way to save 08:32:42 and I don't think it has an editor 08:32:58 you could save ... just gotta write a device driver to do it 08:33:02 nothingmuch: where'd you here apple is ditching OF? 08:33:07 not the gentlist introduction to forth 08:33:11 gentlest even 08:33:21 wtf is OF? 08:33:24 Herkamire: someone told me that the intel switch means OF is going to the bin too 08:33:24 Herkamire: moving to x86, not likely they're using OF 08:33:31 PoppaVic: OpenFirmware 08:33:34 ahh 08:33:49 a bootloader type thingamabob whose environment is forth 08:33:50 #OpenBios is still around ;-) 08:33:50 i'd imagine they'll be using phoenix, award, or AMI 08:33:58 why wouldn't they use OF on x86? 08:34:09 why would they? 08:34:16 I still can't believe the whole damned world is goin' Intel 08:34:18 because it kicks ass 08:34:19 Herkamire: it's probably cheaper to get a PCish bios 08:34:25 switch to x86 means a switch to commodity hardware 08:34:32 cheaper? there's a free implementation 08:34:33 Herkamire: ppc kicks ass too. didn't stop 'em 08:34:39 I mean, hell - they coulda' collaborated with AMD fer cripes sakes 08:34:53 yeah, but they don't make ppc chips, and I understand they were having trouble buying them 08:34:58 problem is, ppc does *not* kick ass in notebooks, and apple felt like it was getting shafted there 08:35:11 ohhh... apple was buying ppc's elsewhere? I was unaware 08:35:12 motorola wasn't keeping up with g4 sales 08:35:21 ibm is totally disinterested in mobile anything, they only care about the POWER series 08:35:33 and mot doesn't even move computers 08:35:40 and I heard a rumor that IBM got less friendly with apple now that apple is competing with IBM on servers 08:35:49 oh they're hardly competition 08:36:01 apple does not manufacture chips 08:36:14 xserves are hardly anything you'd otherwise install a z-series for 08:36:27 and if xserves made it huge, then ibm would be more than happy to sell services for them 08:36:36 maybe it's because ibm isn't into mobile 08:36:46 their desktop roadmap was anemic 08:36:52 their mobile roadmap was *nonexistent* 08:37:08 Herkamire: how expensive is OF in HW? do you just have some bootstrap code and a forth in asm in some rom chip somewhere? 08:37:10 well, if and when they switch, let's hope their goddamnedcosts come down and they figure out how to install decent touchpads 08:37:26 heck that's probably why they chose intel over amd. that and fab capacity 08:37:39 amd's mobile offerings pale next to intel's 08:37:48 nothingmuch: I don't know. it's just a ram afaik 08:37:52 tho i like their desktop, happily running an athlon64 08:37:52 remember: a token-threaded forth in Eprom would be dinky 08:37:54 yes, intel makes wonderful celeron processors! 08:38:04 nothingmuch: I'm pretty sure the hardware is the same as other bios 08:38:08 celeron M will be quite something 08:38:23 nothingmuch: there's a project to make an OF-like bios for x86 machines. you can just flash your bios with it 08:38:32 #openbios or #openboot or something 08:38:39 that's nifty 08:38:43 /j #openbios 08:38:47 s/ram/rom/ 08:38:48 huh. bootforth makes OF kind of not required, i tend to think 08:39:00 whole thing fits on the part of a disk that any bios can read 08:39:05 but enough distraction... on to read minforth... ciao guys! 08:39:29 nothingmuch: try herkforth! 08:39:37 i guess it'd make for a genuine diskless PXE netboot machine 08:39:44 nothingmuch: it's not at all like the others 08:39:44 Herkamire: will do 08:39:45 without special cards 08:40:09 Herkamire: what's your design goal in a nutshell? 08:40:35 nothingmuch: ease of use. consistency to the point where you don't think about the computer 08:40:56 don't think about the interface that is. 08:41:03 if your programming, you'll think about that of course 08:41:12 sounds goo 08:41:15 d 08:41:36 how is it for learning about forth rather than learning just programming in forth? 08:41:58 to my tasts, it's the best programming environment I've used or seen ever 08:42:03 ABOUT is a lot more... "interesting" 08:42:34 nothingmuch: good I think. not excelent. I don't have any medium-level forth tutorials 08:42:51 I've books all over the house that delve into TIL and fig and F83 guts 08:42:51 nothingmuch: it's _great_ for browsing through the source 08:43:50 nothingmuch: if you want to learn about forth in general, I reccomend "starting forth" and "thinking forth" by leo brodie 08:43:51 --- join: onetom (~tom@ns.dunasoft.com) joined #forth 08:44:01 too bad you didn't set the termio stuff ;-/ 08:44:02 books or tut's? 08:44:12 they are books 08:44:12 both execellent books 08:44:29 tings' works are also decent, on f83 and even fpc 08:44:30 at least one is available free online in PDF and/or html 08:44:46 http://thinking-forth.sourceforge.net/ 08:46:38 hot damn, cold beer 08:47:48 Herkamire: I think both ^H and ^? delete from the buffer, but only ^? displays the change 08:48:06 * nothingmuch just found out that ^H actually works in OSX textboxes 08:50:45 nothingmuch: you runing it with ./run ? 08:51:04 nope... ./herkforth001 or something like that 08:51:10 that'll do it 08:51:16 much better 08:51:19 ./run sets up the terminal 08:51:24 and puts it back when you're done 08:51:28 no ^U though ;-) 08:51:36 what's ^U ? 08:51:37 weird 08:51:48 PoppaVic: what? 08:51:52 kill line or something like that 08:52:12 that would be more like using readline() 08:52:16 \ will kill the whole input line (or if it's empty, a word from the source) 08:52:27 nothingmuch: yer mixing shellisms and c'isms with forth 08:53:05 well, i can't help it, i've just taken my first serious look at forth today =P 08:53:26 culture shock takes a while to digest ;-) 08:53:38 forth is strange 08:53:42 fpc had, imnsho, possibly the best danged editor-debug interface I ever saw for console-forth. 08:53:46 ^U iirc is supposet to clear the rest of the line to the _right_ of the cursor, which can't happen in herkforth atm 08:54:04 Herkamire: that's ^K 08:54:05 herkforth is a culture shock from just about anywhere 08:54:07 nothingmuch: i suggest "starting forth". get it from the library if you can find it, otherwise get the online text 08:54:13 nothingmuch: google for "starting forth" 08:54:20 nothingmuch: why so it is :) 08:54:33 the online text isn't quite as nicely illustrated as the dead tree version 08:54:34 could map ^U if you like 08:54:47 tho they do remind me a tad of why's poignant guide to ruby ;) 08:55:09 don't know why. a bit surreal i guess 08:56:23 ^K is of course an emacsism 08:56:27 why's poignant guide was so fun to read, dunno why i stop 08:56:29 ped 08:56:40 i couldn't get into the guide. it is pretty bent tho 08:56:58 sproingie: if you use OSX you'll be glad to know that most of the stuff bash stole from emacs (i don't use emacs, so bash got me used to it) works everywhere 08:56:58 maybe forth could use a similar acid-inspired document 08:57:08 nothingmuch: this should add that keybinding: "comtDNed-init]$15[ w, S" (type exactly without the quotes) 08:57:13 every time I try to ^A in a URL box on windows I pull my hair out 08:57:15 nothingmuch: nope, no osx boxen here 08:57:23 nothingmuch: i just run cygwin 08:57:27 bash is nice to have 08:57:45 Herkamire++ 08:57:55 the output in the block browser thingy is scary, but it works =) 08:58:05 heh :) 08:58:15 anyway, food now 08:58:20 thanks all for a nice chat 08:58:41 there may be a better way to do it once I get better access to the keyboard, but it's very cool to be at the editor and interpreter at the same time 08:59:09 --- quit: sproingie (Remote closed the connection) 09:00:23 heh, every time I use windows at all I pull my hair out 09:00:45 --- join: PoppaVic_ (~pete@0-1pool64-172.nas22.chicago4.il.us.da.qwest.net) joined #forth 09:00:58 --- quit: PoppaVic (Nick collision from services.) 09:01:01 --- nick: PoppaVic_ -> PoppaVic 09:01:06 damned isp 09:02:53 hmm 09:17:57 FreeLSD loader(8) is not stripped. 09:18:26 I calculated Fibonacci numbers there. 09:19:04 It's even extended to accept 'set this=that' style commands. 09:25:40 --- quit: onetom (Remote closed the connection) 09:41:28 --- join: onetom (~tom@ns.dunasoft.com) joined #forth 11:04:02 --- quit: nothingmuch (Read error: 131 (Connection reset by peer)) 11:05:16 --- join: nothingmuch (~nothingmu@yovalk.bb.netvision.net.il) joined #forth 11:11:53 --- part: nothingmuch left #forth 11:13:41 --- join: nothingmuch (~nothingmu@yovalk.bb.netvision.net.il) joined #forth 11:14:45 the next time a weenie like me comes in here, point them to http://www.ultratechnology.com/meta.html 11:14:48 very nice read =) 11:15:22 lemme check 11:16:04 yeah 11:16:20 The term freaks other than forthers, though 11:16:43 eh? 11:16:47