00:00:00 --- log: started forth/01.06.24 00:10:21 --- quit: robert_sleeping (Read error to robert_sleeping[h3n1fls33o898.telia.com]: Connection reset by peer) 00:10:21 --- quit: MrReach (Read error to MrReach[209.181.43.184]: Connection reset by peer) 00:11:46 --- join: MrReach (mrreach@209.181.43.184) joined #forth 01:50:35 --- join: xyzzy (mark4@purplecoder.com) joined #forth 01:50:45 --- nick: xyzzy -> I449r 01:51:00 --- nick: I449r -> I440r_ 02:03:33 --- quit: MrReach (Read error to MrReach[209.181.43.184]: Connection reset by peer) 02:04:21 --- join: robert_sleeping (robost86@h3n1fls33o898.telia.com) joined #forth 02:04:44 --- quit: I440r_ (Read error to I440r_[purplecoder.com]: Connection reset by peer) 02:05:02 --- join: MrReach (mrreach@209.181.43.184) joined #forth 02:05:09 Hi MrReach 02:05:17 * robert_sleeping robert 02:05:21 --- join: I440r_ (mark4@purplecoder.com) joined #forth 02:20:31 --- quit: I440r_ (Read error to I440r_[purplecoder.com]: Connection reset by peer) 02:24:39 --- nick: robert_sleeping -> robert 02:24:46 --- nick: robert -> rob_ert 03:12:32 --- nick: rob_ert -> rob_ert_aw_ay 04:46:12 --- join: adu (andrew@adsl-63-201-90-85.dsl.snfc21.pacbell.net) joined #forth 04:55:42 --- quit: adu (Ping timeout for adu[adsl-63-201-90-85.dsl.snfc21.pacbell.net]) 05:04:35 --- join: adu (andrew@adsl-63-201-90-85.dsl.snfc21.pacbell.net) joined #forth 05:10:47 --- nick: rob_ert_aw_ay -> rob_ert 06:24:50 --- nick: rob_ert -> rob_ert_aw_ay 06:28:58 --- quit: MrReach () 07:07:24 --- quit: adu (IRCStep) 08:40:11 --- nick: rob_ert_aw_ay -> rob_ert 08:50:43 hi rob ert 08:53:00 Hi 08:53:05 =) 08:53:21 I'll have a look at those sites you recommended 08:53:29 and try making a forth compiler 08:55:06 well making a forth compiler is a ways down the road yet :) 08:55:12 even for me it seems :P 08:55:13 brb 08:55:16 ok 09:07:47 --- nick: rob_ert -> rob_ert_eat_ing 10:01:36 --- nick: rob_ert_eat_ing -> rob_ert 10:53:23 --- nick: rob_ert -> rob_ert_aw_ay 11:39:33 --- nick: rob_ert_aw_ay -> rob_ert 12:28:57 --- nick: rob_ert -> Homer 12:29:04 --- nick: Homer -> rob_ert_aw_ay 12:36:38 --- join: futhin (thin@h24-67-113-99.cg.shawcable.net) joined #forth 12:36:47 hola 12:37:01 can somebody tell me if forth can be compiled? as in "no interpreter packaged with bytecodes" ? 12:37:15 is forth a compiled language or an interpreted language? 12:37:49 Hehe 12:37:55 I've asked that a couple of times 12:38:07 I don'y understand the answer 12:38:11 don't 12:38:21 what's the answer? do you remember? 12:38:40 No, but I think I have a log saved of it 12:39:55 can you send me the part concerning it? :) 12:40:18 maybe i'll be able to interpret it for you :) 12:40:30 hmm 12:40:34 ask I440r 12:40:39 can't find it =( 12:40:48 he knows a lot about forth 12:41:13 yeah 12:49:15 --- quit: rob_ert_aw_ay (Read error to rob_ert_aw_ay[h3n1fls33o898.telia.com]: Connection reset by peer) 12:52:03 --- join: rob_ert_aw_ay (robost86@h3n1fls33o898.telia.com) joined #forth 13:33:17 --- quit: I440r (Ping timeout for I440r[purplecoder.com]) 13:58:53 --- quit: futhin (gtg) 14:11:27 --- quit: rob_ert_aw_ay (Ping timeout for rob_ert_aw_ay[h3n1fls33o898.telia.com]) 14:11:27 --- quit: dired (Ping timeout for dired[vitelus.com]) 14:13:06 --- join: rob_ert_aw_ay (robost86@h3n1fls33o898.telia.com) joined #forth 14:13:14 --- join: aaronl_ (aaronl@vitelus.com) joined #forth 14:13:56 --- nick: rob_ert_aw_ay -> rob_ert 14:19:51 --- join: Ales (ahvezda@shell.cybercom.net) joined #forth 14:19:51 --- join: dired (aaronl@vitelus.com) joined #forth 14:19:55 --- quit: aaronl (Read error to aaronl[vitelus.com]: EOF from client) 14:19:57 --- join: I440r (mark4@purplecoder.com) joined #forth 14:19:57 wow chanserv actually bothered to set the topic!!! 14:19:57 shock horror! 14:19:57 heh 14:22:46 --- mode: ChanServ set mode: +o I440r 14:30:45 --- join: s[e]th (jpopcenter@APastourelles-101-1-3-19.abo.wanadoo.fr) joined #forth 14:31:04 hi 14:31:08 --- mode: I440r set mode: +o aaronl_ 14:31:14 --- mode: I440r set mode: +o Ales 14:31:17 --- mode: I440r set mode: +o dired 14:31:20 --- mode: I440r set mode: +o rob_ert 14:31:21 =) 14:31:23 --- mode: I440r set mode: +o s[e]th 14:31:50 are you so sure that's a good idea... 14:31:58 I could be evil. :-) 14:32:30 so could i :) 14:32:46 * rob_ert could be... In theory 14:32:56 evil forth people 14:33:04 go forth and be evil.. 14:33:05 oh wait 14:33:08 Hehe 14:34:12 have you see FARE ? 14:34:31 not today 14:34:40 oh... ur ftrom #tunes ??? 14:34:43 you ARE evil :) 14:34:44 heheh 14:34:48 How many under 35 in this #forth forum? 14:34:53 when for the last time ? 14:34:55 me! 14:35:00 hrm 14:35:02 me! 14:35:04 yesterday 14:35:05 ^^ 14:35:15 I440r: thank ^^ 14:35:32 np :) 14:37:16 me! 14:37:18 aggg 14:37:22 damn history 14:38:24 perhaps it's not a forth's subject but who know about curl ? 14:38:51 this is a forth channel where you can talk about anything you want :P 14:39:09 this isnt #tunes where they get anally retentive if you just MENTION something non tunes related :P 14:39:44 but ive never heared of curl 14:39:48 i dont think 14:39:54 maybe someone mentioned it in here b4 14:39:57 i ferget 14:40:03 ok ;p 14:40:03 its old age u know :) 14:40:14 --- nick: rob_ert -> rob_ert_aw_ay 14:40:21 i'm gonna ask to fare (in tunes' channel) 14:40:23 ^^ 14:40:23 * rob_ert_aw_ay doesn't know fortran very well 14:40:58 and one "upseting" question : 14:43:59 --- quit: s[e]th (Ping timeout for s[e]th[APastourelles-101-1-3-19.abo.wanadoo.fr]) 14:44:49 so anybody doing any app development in forth here? 14:49:47 not yet 14:49:51 need a real forth first 14:55:31 --- nick: rob_ert_aw_ay -> rob_ert 15:07:15 --- quit: rob_ert () 15:19:40 --- join: rob_ert (robost86@h3n1fls33o898.telia.com) joined #forth 15:34:22 --- join: s[e]th (jpopcenter@APastourelles-101-1-3-19.abo.wanadoo.fr) joined #forth 15:54:21 --- quit: s[e]th (Ping timeout for s[e]th[APastourelles-101-1-3-19.abo.wanadoo.fr]) 16:07:36 --- join: adu (andrew@adsl-63-201-89-240.dsl.snfc21.pacbell.net) joined #forth 16:40:27 Hi adu =) 16:41:27 --- quit: adu (Ping timeout for adu[adsl-63-201-89-240.dsl.snfc21.pacbell.net]) 16:57:38 --- join: adu (andrew@adsl-63-201-90-87.dsl.snfc21.pacbell.net) joined #forth 17:31:09 --- nick: rob_ert -> rob_ert_sleep_ing 17:44:52 --- quit: Ales (Leaving) 17:54:23 --- join: TheBlueWizard (tbw@ip-216-25-202-208.vienna.va.fcc.net) joined #forth 17:54:23 --- mode: ChanServ set mode: +o TheBlueWizard 17:54:28 hiya all 17:54:34 --- mode: TheBlueWizard set mode: +o adu 18:19:30 * Trey is idle: BRB 18:19:35 Hmmm. 18:19:53 * Trey has returned 18:20:01 * Trey has returned 18:20:09 Hmmm. 18:20:57 hiya Trey 18:35:14 Howdy TheBlueWizard. 18:35:23 * Trey reads c.l.f 18:36:53 find anything interesting in c.l.f.? 18:39:38 The tail end of a meltdown between Jeff Fox and "everyone else" over wether or not you can have an ANS Forth with a 16bit data stack and a 21 bit return stack. 18:42:58 * Trey is idle: back later. 18:43:25 that's a rather weird architecture to use....it's usually expected to have both data stack and return stack to have same cell size so that >R R> whatever works properly 19:08:04 * Trey has returned 19:08:24 Not really so strange. 19:08:51 >R and R> must move CELL-sized elements between the stacks. 19:09:54 yeah...but the bit size...16....21....I take it you have to use the bigger one, eh? 19:10:41 If you have a 16bit data stack (CELL == 16 bits), you get 5 bits of don't care/don't know when the item moves to the return stack. 19:11:38 When that item comes off the return stack, it gets clipped to 16 bits and you never knew or cared it happened. 19:13:01 sounds dangerous to me....then again... 19:13:15 Not at all. 19:13:28 You may only remove things from the return stack that you put there. 19:58:52 got to go....bye all 19:58:55 --- part: TheBlueWizard left #forth 20:42:19 --- join: cleverdra (jfondren@1Cust175.tnt4.florence.sc.da.uu.net) joined #forth 20:42:19 --- mode: ChanServ set mode: +o cleverdra 20:42:24 --- mode: cleverdra set mode: +o rob_ert_sleep_ing 20:42:29 'Yo =) 20:44:50 dired, karma forth 20:44:50 forth has neutral karma 20:44:53 forth++ 20:44:54 dired, karma forth 20:44:55 forth has karma of 1 20:45:12 1 forth +! =) 20:46:21 o/~ way back in the year one / when you belonged to no one / you didn't stand a chance, son / all your plans were un-done o/~ 20:46:25 (Jethro Tull)++ 20:47:35 I'm going to teach Enth to speak to my speaker, and write a lyric-player in Color Forth. 20:48:19 I guess the speaker will beep rythmically or something. 20:57:47 1 forth +! hehehe 20:57:53 1 20:57:58 1 +!> forth 20:58:01 incr> forth 20:58:02 heh 20:59:24 : ++ dup @ 1+ swap ! ; 20:59:52 I actually had the wrong patch for nasm, i440r. Do you know where the 98e thing is? 21:00:09 ftp://ftp.purplecoder.com/pub :) 21:00:14 its a debian package tho 21:00:22 if u want ill extract it and tgz it 21:00:25 its the linux binaries 21:04:18 the .zip is a deb? 21:04:29 That's the only 98e thing I see. 21:11:52 http://eurosport.ifrance.com/joss/nasm098e.zip 21:12:00 its a debian package 21:12:03 oh 21:12:06 its a zip ? 21:12:15 hehe it was a .deb, maybe iu put the zip in there 21:12:18 hehe 21:12:19 duh 21:12:33 well, that's cool. Above link from somewhere else. 21:14:12 ? 21:17:27 http://eurosport.ifrance.com/joss/nasm098e.zip 21:17:35 Above link from somewhere else. 21:21:21 http://www.linuxassembly.org/asmutils.html -- hee. GNU utils written in assembly! 21:22:52 http://nasm.2y.net/ 21:22:56 dired, nasm is also http://nasm.2y.net/ 21:22:57 OK, cleverdra. 21:23:37 nasm.2y.net is the official nasm i believe but i dont know if its still being developed 21:24:14 What do you mean? nasm isn't being developed anymore? 21:24:27 latest version there: 0.98.08 21:24:28 i think the developers are on permanant holiday hehe 21:24:45 the original author dropped it 21:24:53 oh, hm. 21:25:00 it was taken up by his #2 developer i think.... 21:25:30 Well, nasm should last isforth until it has its own assembler and can metacompile itself :-/ 21:25:38 yes 21:25:50 nasm is just a bootstrap stage thing hehe 21:26:23 You said you don't like postfix assemblers. What about a prefix/postfix assembler? Enth's SASM has a switch that'll change it from postfix to prefix. 21:27:23 that would be good 21:27:24 change it between postfix and prefix 21:27:28 so did pasm 21:27:31 from fpc 21:27:39 but pasm was always 16 bit 21:27:39 Oh, I'm starting you agree with you about the subroutine-threaded Forth thing. 21:27:46 :) 21:27:49 it isnt forth 21:27:58 ret != next 21:28:52 call != nest :P 21:29:02 Today, I was reading documentation on FOSM, which is a vastly cool pattern matcher (o/~ and more! o/~) in Forth... that won't and can't work on a system whose return stack doesn't hold return addresses and such. 21:29:14 and its less efficient space wise 21:29:17 subroutine threaded systems don't use the return stack for that, right? 21:29:51 well i dont know - they might 21:29:59 the processor stack might be the return stack 21:30:05 and a software stack used for parameters 21:30:44 Yeah, the processor stack is apparently better as data stack for direct/indirect, and as return stack for subroutine -- or it's the other way around. 21:31:24 Please elaborate on why you don't think Forth can be subroutine threaded. 21:31:34 ret != next, call != nest? 21:32:02 call is not a nest 21:32:05 ret is not a next 21:32:10 its just not forth 21:32:13 its unthreaded 21:32:46 well, no, it's not threaded. 21:34:13 i dont realy like indirect threading either -- 21:34:23 but i still consider it to be a valid forht model 21:37:08 Why don't you like indirect threading? gforth uses indirect threaded on the Pentium, because it is supposedly faster on that architecture. 21:37:51 i cant see how 21:38:08 how can a pointer to a pointer to a function be faster than a pointer to a function 21:40:33 I dunno. Maybe pentium has an op for it. 21:40:38 Ask the gforth people? 21:40:45 :) 21:40:59 isnt gforth written in c ? 21:42:21 --- quit: aaronl_ (installing RAM) 21:43:21 A very tiny bit of it is, apparently. The C that I've seen is mostly in prim, embedded in Forth. It's... wierd. I actually can't use gforth right now, because I lack a certain header that *** two words *** need. I can remove those two words from prim and from engine/prim.i (normally the later is generate by gforth, but I don't have gforth, see?), but it still wants them (it shouldn't! they are extraneous! unused elsewhere!) and 21:43:23 so... no gforth. 21:43:34 I was only thinking of using gforth to metacompile my own system, anyway. 21:44:23 :) 21:44:44 well if it has a single " <-- iddy biddy piece of c in it i want no part of it 21:44:46 :) 21:47:03 http://www.openhere.com/tech1/programming/languages/forth/implementations/ 21:47:11 isforth gets a mention there hehe he has a link to it :) 21:47:13 wow!!! 21:47:16 im phamus :P 21:47:22 dang better get werkin on it :) 21:48:56 actually, i am working on it indirectly - im reading up on the linux kernel 21:49:09 neway its time for me to go zzz :) 21:49:10 as soon as I can get the bloody thing compiled, I'll help =) 21:49:12 nite dood 21:49:16 yes!!! 21:49:19 that would be cool :) 21:49:20 g'night, i440r 21:49:36 nite :) 21:49:56 tcn has it compiling already - i need his latest sources but he has no internet rite now :( 22:00:16 --- join: aaronl (aaronl@vitelus.com) joined #forth 22:00:24 --- mode: cleverdra set mode: +o aaronl 22:00:28 welcome back, aaron 22:00:37 GARGARGAR 22:00:46 my mainboard SUCKS 22:01:15 it detects 512mb as 256mb 22:01:31 cleverdra: Rick Honessee (sp?) made a fool out of himself on LKML 22:01:36 mainboard? 22:01:39 LKML? 22:01:42 How so? 22:01:44 Hohensee. 22:02:20 ah 22:02:45 he suggested forking the kerenl, droping support for SMP and non-i386 archs, ignoring posix, and using CR+LF 22:03:07 that's interesting. 22:03:19 He's doing this forking himself? 22:03:47 no 22:03:51 he just said it should be done 22:04:03 * cleverdra shrugs. 22:04:25 Wierd. I wonder what his reasons were for CR+LF. 22:07:10 --- quit: cleverdra (Leaving) 23:16:15 --- quit: adu (IRCStep) 23:30:26 --- join: adu (andrew@adsl-63-201-90-87.dsl.snfc21.pacbell.net) joined #forth 23:59:59 --- log: ended forth/01.06.24