00:00:00 --- log: started forth/03.02.17 00:06:07 --- quit: ramnull ("ircII EPIC4-1.1.7 -- Are we there yet?") 00:37:25 --- join: ramnull (~nicad@12-241-145-39.client.attbi.com) joined #forth 00:38:22 s" Feet" constant Feet 00:38:22 s" Inches" constant Inches 00:38:22 : cnvfeet ( n str -- n ) { a } Feet compare 00:38:22 1 = IF a 12 / ENDIF ; 00:38:22 ; 00:38:23 : cnvinches ( n str -- n ) { a } Inches compare 00:38:25 1 = IF a 12 * ENDIF ; 00:38:27 ; 00:38:29 Make any sense? 00:39:38 * ramnull will lurk for a while 00:41:02 --- join: Serg_Penguin (~Z@nat-ch1.nat.comex.ru) joined #forth 00:43:56 Hey Serg, busy? 00:44:42 hi 00:45:05 testing cd-rw drives 01:02:10 --- quit: Kitanin (Read error: 104 (Connection reset by peer)) 01:08:33 --- quit: Soap` (Read error: 54 (Connection reset by peer)) 01:26:56 --- quit: Serg_Penguin () 01:27:23 --- part: ramnull left #forth 01:44:21 --- join: Serg_Penguin (~Z@nat-ch1.nat.comex.ru) joined #forth 01:47:23 --- quit: Serg_Penguin (Client Quit) 02:45:11 --- join: Kitanin (~clark@SCF61185.ab.hsia.telus.net) joined #forth 03:15:08 --- quit: Kitanin (Read error: 104 (Connection reset by peer)) 04:45:26 --- join: Kitanin (~clark@SCF61185.ab.hsia.telus.net) joined #forth 05:02:43 --- quit: Kitanin (Read error: 104 (Connection reset by peer)) 05:08:29 --- join: Serg_Penguin (~Z@nat-ch1.nat.comex.ru) joined #forth 05:08:49 --- quit: Serg_Penguin (Client Quit) 05:23:40 --- join: Serg_Penguin (~Z@nat-ch1.nat.comex.ru) joined #forth 05:42:20 Serg_Penguin, hi. 05:42:42 I lent your account to a few guys, you might want to change the password. 05:43:07 They needed somewhere to IRC from 05:45:57 done 05:46:28 so, how can i IRC from it ? 06:17:03 Start irssi :) 06:38:25 --- quit: ChanServ (Shutting Down) 06:45:37 --- join: Kitanin (~clark@SCF61185.ab.hsia.telus.net) joined #forth 06:49:00 --- join: serg (~serg@h138n2fls31o965.telia.com) joined #forth 06:49:17 z 06:49:42 hey Serg_Penguin ! 06:52:35 --- join: ChanServ (ChanServ@services.) joined #forth 06:52:35 --- mode: leguin.freenode.net set +o ChanServ 06:52:35 --- mode: ChanServ set +l 83 06:53:52 i did it ! 06:58:37 --- quit: serg ("leaving") 06:59:44 Hah. 06:59:58 Privet, Sergej ;) 07:00:54 :) 07:01:01 seems like running home 07:04:40 --- join: flyfly (~marekb@mail.melzer.cz) joined #forth 07:04:40 --- quit: Kitanin (Read error: 54 (Connection reset by peer)) 07:14:32 --- nick: flyfly -> flyout 07:16:42 --- join: TheBlueWizard (TheBlueWiz@ip-216-25-202-152.vienna.va.fcc.net) joined #forth 07:16:48 hiya all 07:17:21 --- quit: Serg_Penguin () 07:42:59 Hi :) 07:43:18 hiya Robert :) 07:49:51 any of you use qmail? 07:50:12 nope...sorry 07:50:22 not me, that is 07:50:26 :P 07:55:29 I don't... 08:24:05 --- join: I440r (~mark4@ip209-183-83-44.ts.indy.net) joined #forth 08:25:24 hiya I440r!!! :) 08:36:53 tbw!!! :) 08:37:01 :) 08:37:31 whussup ? 08:37:33 :) 08:37:38 how's life? today's Fed. holiday...plus DC area is heavily snowed in...hope tomorrow Fed gov't is closed ;) 08:37:56 lol 08:38:10 the snow is just an exscuse not to go to to work 08:38:24 yupyupyup :) 08:38:28 heh 08:38:41 it didnt snow here, it just sleeted for 10 hours or so 08:38:51 about an inch :P 08:39:26 that makes a mess on roads... :P 08:40:12 ya 08:41:45 here...at first it was freezing rain, then turns into heavy snowing, and this afternoon it should be a light rain...then tonight it will become cold...the news on TV said it was the sixth biggest snowfall ever to hit DC area 08:42:40 coultnd happen to a better bunch of people 08:42:40 :P 08:42:55 heh 08:46:34 what's the latest news on IsForth? 08:47:19 ive been slowly working on a memory manager for her 08:47:41 its almost done. allocate is complete and theres only one more word left to write for "Free" 08:47:47 then i gotta test it 08:47:52 the free part i mean 08:47:59 cool 08:48:05 oh - i sould prolly write a "reaalloc" or something 08:48:23 16 byte granularity instead of 4k 08:48:24 sounds like you're nearing the release point 08:48:42 realloc is nice! but it is a bit tricky to implement 08:49:01 4k is too much...16 bytes is better 08:55:37 --- quit: flyout (Read error: 113 (No route to host)) 09:00:02 --- quit: I440r (Excess Flood) 09:00:42 --- join: I440r (~mark4@ip209-183-83-44.ts.indy.net) joined #forth 09:01:07 --- join: Kitanin (~clark@SCF61185.ab.hsia.telus.net) joined #forth 09:01:46 hiya I440r again 09:01:48 fscking network cable keeps disconnecting from my laptop 09:01:49 hiya Kitanin 09:01:49 grr :P 09:01:58 ah 09:26:53 --- quit: Kitanin (Read error: 54 (Connection reset by peer)) 10:26:17 tbw are you still there ? 10:27:06 I'm here 10:27:43 whassup? 10:37:03 --- join: male (~male@cpe-024-033-024-002.midsouth.rr.com) joined #forth 10:37:30 --- quit: male (Client Quit) 11:08:40 --- join: Kitanin (~clark@SCF61185.ab.hsia.telus.net) joined #forth 11:11:22 hiya Kitanin 11:35:18 it's 75 degrees here 11:35:21 blue skies 11:35:31 and here I am inside 11:36:49 nice 12:05:02 dammit - where the heck are you ? 12:15:43 Not on earth. 12:16:07 75 degress... maybe the moon right after sunrise :) 12:16:30 * Robert will NEVER accept the Farenheit temperature scale. 12:42:30 --- quit: I440r (Read error: 60 (Operation timed out)) 12:42:52 --- join: I440r (~mark4@ip209-183-83-44.ts.indy.net) joined #forth 12:45:30 hiya I440r again :P 12:45:45 ~cluebat I440r's ISP 12:46:44 its not my isp 12:46:53 * TheBlueWizard watches apt walks into here as a guest, whaps I440r's ISP with a cluebat until it makes promises not to hose I440r 12:46:54 its my network connector on my laptop 12:46:56 oh? 12:47:00 if i breath it disconnects 12:47:03 hmm...ok 12:47:13 yow...that bad, eh? 12:47:19 ya :P 13:05:38 --- quit: Kitanin (Read error: 54 (Connection reset by peer)) 14:47:43 gotta go...bye all! 14:48:14 --- part: TheBlueWizard left #forth 15:01:43 --- join: Kitanin (~clark@SCF61185.ab.hsia.telus.net) joined #forth 15:16:01 --- quit: TreyB (leguin.freenode.net irc.freenode.net) 15:16:27 --- join: TreyB (~trey@cpe-66-87-192-27.tx.sprintbbd.net) joined #forth 15:38:24 --- join: ramnull (~nicad@12-241-145-39.client.attbi.com) joined #forth 15:38:33 Whats up? 15:59:10 hi 15:59:11 --- quit: Kitanin (Read error: 104 (Connection reset by peer)) 15:59:18 ramnull is new in here ? 15:59:29 or is that just a new nick ive not seen yet ? heh 16:07:41 --- quit: ramnull (Read error: 60 (Operation timed out)) 17:00:45 --- quit: Klaw () 17:14:21 --- join: ramnull (~nicad@12-241-145-39.client.attbi.com) joined #forth 17:14:29 What's up? 17:15:20 Hows this look? : addup depth tuck 0 +DO rot + LOOP ; 17:18:47 erm rot rotates out the thrid item 17:18:51 not the nth item 17:19:20 Yeah. I'm trying to preserve the depth value. 17:19:36 So there should be two items on the stack at the end. 17:20:29 you lost me. what are you trying to do exactly ? 17:20:53 Trying to figure out how the stack works basically. 17:21:12 Adding up a bunch of numbers that have been pushed on the stack. 17:21:52 how many numbers ? 17:22:18 Any amount. Thats what I'm using depth for. 17:22:32 ok 17:22:36 ramnull : I'd do this: : addup begin depth 1 <> while + repeat ; 17:22:45 and you want the result and the number of numbers added ? 17:22:48 ok 17:22:48 Adds up all the numbers on the stack. 17:22:59 (If that is what you wanted to do) 17:23:20 : xyzzy depth dup>r 0 do + loop r> ; 17:23:31 you might need a dup>r 1- 0 do 17:24:14 Well, 5 7 6 2 gives me 24, which isnt correct. 17:24:46 ramnull : The one I pasted gives 20, which is corect. 17:25:20 I wouldn't use a do loop in this situation. 17:25:49 Must have had an extra number on the stack. 17:26:04 How would you do it? 17:26:13 : addup begin depth 1 <> while + repeat ; 17:26:27 * ramnull nods 17:26:47 But if I wanted to preserve the depth value until the end, I'd have to use rot? 17:26:57 : z depth dup>r 1- 0 do + loop r> ; 17:26:59 works 17:27:32 depth >r begin .......until r> 17:27:50 ramnull : You mean you want to Leave all those items on the stack? 17:28:16 So 7 8 2 addup .s would give 7 8 2 17 17:28:16 ? 17:28:39 I want to use depth to control how many times the loop executes, and then use depth for a further calculation like averaging or something. 17:28:43 no he jsut wants to have the result and the number of items added returned 17:29:36 ramnull Oh, well then yeah, do this : addup dup >r begin depth 1 <> while + repeat r> ; 17:30:01 You'll be left with the number of items added on the top, and the sum below. 17:30:16 r> and >r move items from and to the return stack, respectively. 17:30:19 no : addup depth >r begin depth 1 <> whole + repeat r> ; 17:30:30 Er ya, depth not dup 17:31:30 The tutorials said I should avoid the return stack until I've gotten the data stack figured out. :p 17:31:44 The return stack is another stack you can use in your words, however you have to be careful to leave the return stack as it was when you entered the word. 17:31:55 I see. 17:32:03 ramnull : Well, it would greatly simplify this problem. :) 17:32:21 So anything I put on the return stack has to come off before I leave the word. 17:32:32 Exactly. 17:32:46 Aaaa...I see. 17:33:05 ramnull : Unless you know what you're doing. 17:33:33 But generally you'll want to take off everything you put on. 17:33:44 Well, it'll be a while until I know what I'm doing. But I figure following the KISS philosophy will accelerate things. 17:33:56 Heh. True. 17:35:18 Hmmm...I'm also curious about Block files as opposed to regular Operating Sytem file access. Is there a way to use Block files on an Host system? 17:35:30 ramnull : Yes, but please don't. :) 17:35:36 Block files are almost completely obsolete. 17:35:44 Most modern forths support direct writing to files. 17:36:01 But I was told that thier faster than regular file accesses. 17:36:11 Ones on top of an OS, that is. 17:36:32 ramnull : No, they're only slightly faster. 17:36:42 Gotcha. 17:37:01 Gotta keep it "real". Heh. 17:37:05 And that's in the best case. Often filesystems will do clever buffering tricks which will in fact *speed up* file writes, making them faster than blocks. 17:37:19 :) 17:37:24 I see. 17:37:49 Out of curiosity, what tutorial are you reading? 17:37:57 This whole stack thing is gonna be great once I figure it out. 17:38:12 Actually I'm looking over several tutorials. 17:38:18 Oh ya, cool. 17:38:39 --- join: Kitanin (~clark@SCF61185.ab.hsia.telus.net) joined #forth 17:38:57 Well yeah, the stack is a very powerful concept. Most languages use a stack to a degree, but forth definitley offers more flexibility when dealing with the stack. 17:39:25 --- join: I440r_ (~mark4@ip209-183-83-118.ts.indy.net) joined #forth 17:39:38 Reading Real-Time Forth at the moment. 17:39:46 Oh ya... 17:40:15 Also got Nobles "Forth Primer". 17:40:44 And I've been reading over Phil Koopmans web pages. 17:40:56 Cool. Well the most important concepts in forth are probably the dictionary and the stack. 17:41:25 Is the dictionary easier to use or faster than straight memory accesses? 17:41:55 ramnull : No, the dictionary is a method for finding locations of memory *at compile time*. 17:42:09 When the program is running, it directly addresses those pieces of memory. 17:42:09 I'm primarily used to Wirth languages.(Pascal, Ada, Oberon, etc...) 17:42:26 Aaah, I see. 17:42:35 Heh. Well forth is radically different from those languages. 17:42:50 Sort of like an embedded linker? 17:43:08 ramnull : Sory of, yeah. Sort of like an incremental compiler and linker in one. 17:43:34 In order to understand the dictionary, you must understand forth "threads". 17:43:40 I can use it to create self-modifying code. 17:43:56 ramnull : Yes, you certainly could. 17:44:17 In fact parts of the forth kernel are self modifying. DEFERed words are the most common example. 17:44:30 I imagine forth threads are to Unix threads as Ada tasks are to Unix threads. Entirely different ideas. 17:45:10 Possibly. I'm not sure what an ada task is, but yes: forth threads are very different from unix threads. 17:45:32 Take a word like square. : square dup * ; 17:46:00 Well, an Ada task links with the Native "threading" code(if it exists) or else uses it's own inherent tasking scheme, which may or may not work. 17:46:05 Once compiled, that word takes exactly 3 words of memory. (enough for 3 addresses). 17:46:30 ramnull : Er, well forth threads have nothing to do with multitasking. 17:46:52 I know. Neither does Adas. Heh. 17:47:05 Square would look like this: [address of DUP][address of *][address of EXIT] 17:47:07 Oh. :) 17:47:16 A forth thread maintains seperate dictionaries? 17:47:32 i.e. One for each thread? 17:47:50 Er, not exactly... 17:48:06 Once you become more familiar with forth, check out this page. Read the "Moving Forth" articles. 17:48:08 www.zetetics.com/bj/papers/ 17:48:17 It explains forth threads well. 17:48:18 * ramnull nods 17:48:23 I'll do that. 17:48:34 OK, cool. I'll be back later. :) 17:48:37 Good luck. 17:48:41 Laters then. Thanks. 17:49:08 I wonder if theres a way to make Forth support seperate compilation. 17:50:22 Gotta go practice. Be back around 3:30am, after work. 17:50:34 Third shift sucks ass. 17:50:56 --- quit: ramnull ("ircII EPIC4-1.1.7 -- Are we there yet?") 18:03:39 --- quit: I440r (Read error: 110 (Connection timed out)) 18:29:08 --- quit: I440r_ ("Reality Strikes Again") 18:29:09 --- quit: Kitanin (Read error: 104 (Connection reset by peer)) 20:09:44 --- join: Kitanin (~clark@SCF61185.ab.hsia.telus.net) joined #forth 20:17:14 --- join: Speuler (~l@mnch-d9ba4691.pool.mediaWays.net) joined #forth 20:19:11 g'd morning 20:22:47 my shellscript-forth just successfully executed the first forth word 20:23:06 bash-forth :) 20:23:37 nop nop nop lit 10 sec bye 20:24:15 --- quit: skylan ("Reconnecting") 20:24:21 --- join: skylan (sjh@Riverview75.tbaytel.net) joined #forth 20:33:58 --- join: Soap` (~flop@202-0-42-22.cable.paradise.net.nz) joined #forth 21:11:01 --- quit: Speuler ("BitchX-1.0c19 -- just do it.") 22:03:13 --- quit: Kitanin (Read error: 104 (Connection reset by peer)) 22:32:47 --- join: serg (~serg@h138n2fls31o965.telia.com) joined #forth 22:33:39 --- join: Serg_Penguin (~Z@nat-ch1.nat.comex.ru) joined #forth 22:34:30 Ñ ÐÉÛÕ ÐÏ-ÒÕÓÓËÉ ! 22:34:56 âñ¸ ÿñíî, ïðîáëåìû ñ êîäèðîâêîé... 22:35:19 --- part: serg left #forth 23:59:59 --- log: ended forth/03.02.17