00:00:00 --- log: started forth/02.09.27 00:04:26 --- join: yeahright (~proteusgu@24-197-147-197.charterga.net) joined #forth 00:04:31 --- quit: proteus (Read error: 110 (Connection timed out)) 00:35:48 --- join: Kitanin (~clark@SCF61185.ab.hsia.telus.net) joined #forth 01:04:00 --- quit: yeahright (Read error: 110 (Connection timed out)) 01:04:42 --- join: yeahright (~proteusgu@24-197-147-197.charterga.net) joined #forth 01:50:14 --- quit: Kitanin (Read error: 104 (Connection reset by peer)) 02:04:01 --- join: proteus (~proteusgu@24-197-147-197.charterga.net) joined #forth 02:04:53 --- quit: yeahright (Read error: 110 (Connection timed out)) 02:29:06 --- join: onetom_ (~tom@novtan.bio.u-szeged.hu) joined #forth 02:40:03 --- quit: onetom (Read error: 110 (Connection timed out)) 03:04:29 --- join: yeahright (~proteusgu@24-197-147-197.charterga.net) joined #forth 03:04:43 --- quit: proteus (Read error: 110 (Connection timed out)) 03:30:05 --- join: Kitanin (~clark@SCF61185.ab.hsia.telus.net) joined #forth 04:00:55 --- quit: Kitanin (Read error: 104 (Connection reset by peer)) 04:04:03 --- quit: yeahright (Read error: 110 (Connection timed out)) 04:46:56 --- join: yeahright (~proteusgu@24-197-147-197.charterga.net) joined #forth 05:00:41 --- join: LuckyPhil (~phowlett@CPE-203-45-248-201.qld.bigpond.net.au) joined #forth 05:30:15 --- join: Kitanin (~clark@SCF61185.ab.hsia.telus.net) joined #forth 05:30:16 --- quit: LuckyPhil (Read error: 104 (Connection reset by peer)) 05:53:47 --- quit: Kitanin (Read error: 104 (Connection reset by peer)) 05:54:57 --- join: jacereda (~jacereda@VA1-1G-u-0041.mc.onolab.com) joined #forth 05:55:18 hi all 06:03:31 --- quit: yeahright (Read error: 110 (Connection timed out)) 06:03:48 --- join: yeahright (~proteusgu@24-197-147-197.charterga.net) joined #forth 06:13:46 --- join: Herkamire (~jason@wsip68-15-54-54.ri.ri.cox.net) joined #forth 06:25:18 --- quit: yeahright (Read error: 104 (Connection reset by peer)) 07:02:07 --- join: proteusguy (~proteusgu@24-197-147-197.charterga.net) joined #forth 07:17:21 --- join: cleverdra (julianf@0-1pool36-6.nas2.florence1.sc.us.da.qwest.net) joined #forth 07:22:33 Hello, all. 07:30:29 --- join: Kitanin (~clark@SCF61185.ab.hsia.telus.net) joined #forth 07:46:46 --- join: tathi (~josh@wsip68-15-54-54.ri.ri.cox.net) joined #forth 07:51:31 tathi :) 08:01:10 re 08:03:33 Hi, ianni. 08:04:05 --- quit: proteusguy (Connection timed out) 08:04:34 --- join: proteusguy (~proteusgu@24-197-147-197.charterga.net) joined #forth 08:36:00 --- quit: Kitanin (Read error: 104 (Connection reset by peer)) 08:41:51 --- quit: proteusguy (Remote closed the connection) 09:01:57 --- join: Speuler (~l@mnch-d9ba42b6.pool.mediaWays.net) joined #forth 09:02:06 g'day 09:03:40 busy here :) 09:03:47 yeah 09:03:55 its weekend 09:04:00 & u know how it goes 09:04:32 case friday of ... 09:05:45 1tom, what happened to your bot ? 09:06:50 1tom: here 10 dump \ does this work too ? 09:14:33 i gave up monitoring it 09:14:39 --- nick: onetom_ -> onetom 09:15:07 & my net connection was interrupted terribly often 09:19:50 ah 09:20:26 2 bad 09:24:03 * Robert smells some "onetom's English". 09:24:19 * Speuler adapts easily 09:24:56 4 u i do nething :) 09:25:07 Heh. 09:25:22 even submit to weird spelling 09:25:42 4midable 09:41:41 heh 09:50:36 duz funnetik spelling bahther yoo? 09:50:47 not @ all 09:51:07 gr8 :) 09:51:14 only, phonetic spelling looks different, depending on your source language 09:51:43 yep 09:51:58 if ei wudd spell fonetikli it wudd lukk werri diferent indihd 09:52:40 problem is we don't have enough vowels :) 09:54:06 y r u thinking th@ ? 09:54:21 * Robert runs away. 09:54:56 --- nick: Speuler -> Starving 09:55:14 * Robert just ate. 09:55:28 I think there's about 15 vowel sounds in inglish (I just counted 11, and I probably missed some) and we only have 5.5 vowels 09:55:40 5.5? 09:55:51 * Robert wonders how that half vowel looks like. 09:55:51 aeiou and sometimes y 09:56:08 Hm 09:56:20 that's more a problem with american ... always want to use more than they have :) 09:56:22 a has 5 different sounds 09:56:22 We have: aeiouyåäö 09:56:27 and anyway, normal english is 97%+ phonetic 09:56:37 it's just there are somewhere around 44 rules :) 09:57:05 There are too many funny spellings. 09:57:10 tathi: disagree 09:57:21 Where germans have "ie", you have either "ei" or "ie"... confusing. 09:57:25 tathi: it may look phonetical for native english speakers 09:57:33 starving - it doesn't. 09:57:36 but it's not if your native lang is diff 09:57:56 oh, sorry, I thought starving was referring to his 'if ei wudd' 09:58:02 English spelling is messed up. Totally. 09:58:12 Robert - it'll never be fixed =) 09:58:29 yes, the "if" is very phonetic 09:58:29 well, that's what the research says 09:58:39 same as "in" 09:58:40 I don't remember the details 09:58:44 or "of" 10:00:04 cleverdra: Bad idea to mix french and german spelling :-) 10:00:06 consider the "a" in "plaster" "waste" "bad" 10:00:19 all different ... 10:00:23 Robert - french is popular, too. 10:00:35 "maggot" 10:00:35 Robert - err, misread. I'm distracted :-/ 10:00:52 "ahh" 10:01:07 cleverdra: Er.. peanut butter and ketchup are both popular, but you still don't mix them. Besides, swedish spelling is messed up too, but not as much as the English. 10:01:09 Herkamire - 'ahh' is an onomonopeia. 10:01:48 an interjection 10:01:49 Of course, English was nobody's particular 'idea', so we've nobody to hang for it. 10:01:54 you're an onomonopeia ;) 10:02:07 starving - that it's one does not eliminate it as the other. 10:02:09 We *could* hang a randomly chosen englishman. 10:02:25 Just to show we support the war on linguistic terror. 10:02:57 lets learn shrdlu, or esperanto, or something non-imperialistic 10:03:11 English isn't imperialistic. 10:03:24 you say 10:03:34 starving - just like 'you said' it was? 10:03:41 deed in 10:03:42 the US is hopeless ;) we can't even seem to switch to the metric system 10:03:43 Lojban is nice, too. /me looks up shrdlu. 10:04:26 interlingua 10:05:06 Herkamire - it's used often enough in science and business. Mixing the two systems has caused trouble =( 10:06:23 Heh. 10:06:32 Using anything but the SI system is madness. 10:06:40 Robert - ever buy a pint of beer? 10:07:10 cleverdra: No. If I would buy beer at all, I'd buy 1/3 litre bottles. 10:07:38 Robert - ah, OK. I know that England still has 'pints' of beer. 10:07:50 Never been to England :) 10:07:50 1/2 and 1/3 liters are standard mesures for beer here 10:08:02 except the octoberfest. its 1 liter there 10:08:06 Hehe. 10:08:41 that's about 1.76 pint 10:08:59 cleverdra: didn't we loose some space ship or satalite or something because NASA was using US measurements? 10:09:12 Herkamire - a mars probe, at least. 10:09:18 "ever had 1.76 pint on the octoberfest" ? 10:09:33 Herkamire - and it wasn't that they were using 'US measurements', but because they were silently inconsistent about what kinds of measurements they used. 10:10:00 cleverdra: Does _anyone_ use the US system for scientific use? 10:10:03 Herkamire - somebody forgot to convert to metric, I think. 10:10:08 Robert - I hope not. 10:10:18 Rober - the US doesn't use it for scientific use. 10:10:32 Hmm... well, then it's a mystery how this could happen. 10:10:42 (With the Mars probe) 10:11:12 Robert: NASA... 10:11:14 Robert - somebody at NASA, apparently, wasn't thinking in metric and forgot that he wasn't. 10:11:50 how many pints go into a gallon ? 10:12:01 8 10:12:20 what's the next smaller unit to pint ? 10:12:29 cup 10:12:40 1/8 of a pint ? 10:12:46 hmm, a pint is 4 cups I think 10:12:48 I don't know 10:12:51 rofl 10:12:54 * cleverdra doesn't understand English liquid units at all. He knows that 'pint' is smaller than 'gallon'. He has seen enough gallon-units of milk to have an idea of how much liquid that is. 10:13:10 see, that's a major problem with the US system. sitizens that were brought up with it don't even know the whole thing 10:13:13 cleverdra: Who the hell measures the speed of light and such things in miles per hour? :-) 10:13:27 Herkamire: Heh. 10:13:33 few people know how many tablespoons in a cup 10:13:36 light is 186,000 miles per second 10:13:37 Robert - why do you keep asking me these questions? Nobody does. 10:13:38 :) 10:13:41 * Starving was considering to adopt microcenturies as time measurement unit 10:14:01 cleverdra: Well... I don't know. It just seems so ridicilous someone at NASA did. 10:14:23 Herkamire: I wouldn't like to use a measurement system using another base than my native number system. 10:14:32 Herkamire - I was never taught the English system and I never had need to learn it -- contrast the metric system, which I learned in school (physics/chemistry classes, primarily). 10:14:49 Robert: it's worse than that. it doesn't even have a consistant base. 10:15:09 Herkamire: Hehe... right. 10:15:09 --- join: Kitanin (~clark@SCF61185.ab.hsia.telus.net) joined #forth 10:15:10 1 microcentury is about 52 minutes 10:15:24 Robert - like how you measure time? 10:15:33 1 nanocentury about 3 seconds 10:16:11 cleverdra: For scientific purposes, seconds. Everyday use still uses hours/minutes/seconds :-/ 10:16:21 Robert - I'll get back to you in a megasecond. 10:16:46 about 12 days ? 10:16:47 cleverdra: That's a rather long time :-) 10:16:50 Robert =) 10:17:16 Robert - yes; I'm not leaving. 10:17:26 Yeah, I know. 10:17:49 starving - it would seem better to use 'millenia' or 'year' as the base. 10:17:51 Well... at least they could adjust hours and minutes. 10:18:13 one microlightyear -> 150 km ~ 90 miles 10:18:15 Robert - why? 10:18:29 Starving - there are entries in the Jargon file about such units, BTW =) 10:18:33 The problem is that we don't want different times different days :) 10:18:39 cleverdra: To use base 10. 10:19:09 Robert - what's the point of that? 10:19:28 scalability 10:20:29 I say 1 day 10:20:46 cleverdra: Counting with time will get a lot easier. 10:20:57 I'd say it's much more important to have the units line up with days, than years. 10:21:00 cleverdra: (Unless you count your time in seconds after 1970) 10:21:18 Yes... 10:21:33 Then we could count time in days :-) 10:21:38 http://www.m-w.com/mw/table/weight.htm has most of the more common units of measurement... :) 10:23:23 * cleverdra wonders if he can move from ignorance to a nice GUI program using bigForth in less than 4 hours. 10:25:36 Has anyone here used bigForth? 10:25:38 Ik ga uit. Doei. 10:25:43 tot kijk 10:25:46 de mazzel 11:09:11 * Robert is back! 11:26:47 : get-new-line ( -- ) 11:26:47 line-buffer 1+ $ff expect span @ line-buffer c! 0 span @ line-buffer 1+ + c! ; 11:26:51 Why isn't that working? 11:26:55 Hmm.. 11:27:01 looks greek to me :( 11:27:03 I should check what the output is there, eactually. 11:29:42 --- quit: Shain ("ircII+tkirc2") 11:36:03 --- join: XeF4 (photohypon@12-245-111-146.client.attbi.com) joined #forth 11:36:09 Hi XeF4. 11:37:52 hi 11:38:21 --- join: tcn (tcn@tc3-login30.megatrondata.com) joined #forth 11:38:47 tcn :) 11:38:47 Hrm. 11:39:11 * Robert wants to get backspaces using "key". 11:42:45 oh hi 11:43:06 Hrm. 11:43:13 * Robert wonders how to do that in IsForth. 11:43:31 If that's not possible, I want to input a line with some other word. 11:43:38 "expect" fucks up. 11:43:45 For some reason, it 11:43:58 For some reason, it's just returning without any key being pressed sometimes. 11:45:15 heheh.. prolly has to do w/ nonblocking i/o 11:46:12 in nonblocking mode it's possible to read & get nothing, so you have to check for that.. don't think i440r's figured that out quite right. 11:48:07 "expect" does non-blocking I/O? 11:49:07 Hmm.. I just discovered a stupif bug. 11:49:09 Might be it. 11:49:55 you can't do key? in blocking mode 11:50:16 actually you could, using select() 11:50:40 that would make a lot more sense 11:55:09 if you leave it in blocking mode, KEY and EXPECT would work right.. KEY? would just require a select() or pollfd() 11:57:11 Well.. 11:57:22 I think I found that error, it was somewhere else :-/ 11:57:42 key? _is_ using poll. 11:57:52 oh.. hehe 12:03:33 hey check out these pictures someone sent me: tunes.org/~tcn/tmp 12:04:34 * Robert checks. 12:05:47 Hah :D 12:05:59 heh, that just gave me an idea for the "pointing finger" mouse cursor :) 12:06:35 *finally* I fixed this damn bug. 12:06:43 * Robert has a nice little Forth program running. 12:07:15 what's it do? 12:07:31 It's a Forth. 12:07:37 Written in 100% Forth :P 12:07:46 Slow as hell, but kind of neat anyway. 12:07:52 image011 is beautiful =) 12:09:03 I like the SOTP sign :) 12:09:10 ooops, there is no image014 12:09:16 Robert - why should it be slow? 12:09:32 Robert - rather: why is it slow? 12:09:43 what's it do, robert? 12:14:23 * tcn slaps his forehead 12:20:53 so it's slow because it's written in forth 12:22:20 --- part: cleverdra left #forth 12:23:50 tcn: Well, it is a ``Forth in Forth'', so it should be a little slow... 12:24:45 Kitan: an unoptimized threaded-forth-in-threaded-forth would be a little slow, but there is no reason eg.. an optimizing native-code forth written in forth should be slow 12:25:04 a C in C isn't slow 12:28:13 +er than a C in asm 12:29:19 later ya'll.. i'm gonna shut this thing off 12:29:51 --- join: I440r (~mark4@1Cust136.tnt2.bloomington.in.da.uu.net) joined #forth 12:30:02 --- join: jamc (~user@as3-6-8.asp.s.bonet.se) joined #forth 12:30:02 hi ppl 12:30:10 eek we almost have as many people in here today as when chuck was here heh 12:30:21 hey i440r.. you caught me on the way out 12:30:26 lol 12:30:36 hey tcn write me that assembler man 12:30:42 i realy dun wanna 12:30:53 grr its like got me all tied in knots :P 12:30:53 look: tunes.org/~tcn/tmp 12:31:24 why don't you try not touching a computer for a month 12:31:43 tcn i DID that heh 12:31:51 lol 12:31:51 well i didnt code for a while 12:31:56 btw. which one is you L:) 12:33:16 that fedx verses ups is sweet man :) 12:33:16 XeF4: Agreed. 12:33:21 hehe 12:33:29 i'm the one going 169 in a 50 :) 12:34:16 who is that clear-headed fellow preaching the value of reading, writing and arithetic? 12:34:46 what's up w/ the reporter & the plumber? 12:35:34 she's thinking "what the hell is the cameraman laughing about?" 12:35:41 i think thats a doctored picture 12:36:03 the reading/writing one 12:36:17 all they needed to do was move everything after the M over a little and delete the M 12:37:00 and i bet the donutland sign was pasted in over the top of a police station :P 12:37:03 oh hehe, i didn't even realize what was so funny 12:38:09 all of these are perfectly believable though :) 12:38:21 ya 12:39:01 but the sign isn't quite normal with the camera and the text _is_ perspective correct (probably nothing photoshop couldn't fix, though) 12:39:54 i zoom in but it's kinda hard to tell anything with jpeg's because of the 8x8 grid 12:43:35 --- quit: jamc (Remote closed the connection) 12:43:39 is 1.09b the latest isforth? 12:44:26 yes 12:44:47 dont use my structures code in there or the text windowing code 12:44:47 im "fixing" it 12:45:24 --- join: jamc (~user@as3-6-8.asp.s.bonet.se) joined #forth 12:46:42 rotten.com is fucking sick.. i think that donutland photo is the ONLY exception! 12:49:06 you click on something that looks relatively safe and it's a maggoty rotting corpse 13:07:19 --- quit: jacereda (Read error: 110 (Connection timed out)) 13:07:23 --- quit: tcn (Read error: 104 (Connection reset by peer)) 14:09:58 Hrm. 14:10:08 nobody: It's slow because it's written in Forth, yes. 14:12:47 rob: why? I want to know? 14:12:51 ! even 14:13:25 Hehe. 14:13:47 Extra calls to get things done. 14:14:25 It's like letting an interpreter interpret an interpreter, then that last interpreter wouldn't be quite as fast :) 14:14:40 create name-+ ," +" 14:14:40 : [w-+] ( n1 n2 -- n1+n2 ) 14:14:40 ppop ppop + ppush ; 14:14:53 Do you think that's as fast as one "add" instruction? :-) 14:15:19 well yes, if your forth uses some sort of (inefficient) threading 14:15:43 You bet it does! 14:15:53 Indirect threaded code even :-) 14:20:24 --- nick: Starving -> Speuler 14:22:53 * Speuler releases a satisfied "burp" 14:23:05 :) 14:23:19 blood drain mode 14:25:19 --- quit: tathi ("leaving") 14:41:29 --- quit: Chef_ ("Client Exiting") 14:56:06 --- quit: Herkamire ("leaving") 15:02:18 any plans for an isforth glossary? 15:02:55 heh therse a script by hpr in the asmsrc dir 15:03:02 i PLAN on doing a complete HELP system 15:04:25 Cool! 15:04:54 Will it be done before the end of this decade? 15:05:34 whee! the script even works 15:42:36 hehe 15:43:20 I440r: you need to work on freebsd and sockets 15:43:26 so that i can start using forth :P 15:59:37 --- quit: Kitanin (Read error: 104 (Connection reset by peer)) 16:22:31 klaw hehe yea :) 16:22:36 sockets will be in the next release 16:22:42 cant promis when bsd will work tho 16:25:49 then lie to me 16:28:28 hehe 16:28:38 it wil be ready in about 30 seconds :) 16:29:17 & u r traveling nearly w light speed relative 2 us 16:30:09 so weeks elapse 4 us until that 30s passes 4 ya ;) 16:31:09 uknow, time stretch effect.. 16:54:43 klaw do you code x86 assembler ? 16:55:08 --- quit: jamc () 16:57:31 --- join: Herkamire (~jason@ip68-9-58-75.ri.ri.cox.net) joined #forth 16:58:52 1 2 + . 3 16:58:52 : fun 5 + ; 16:58:53 4 fun . 9 16:58:58 Look what my Forth can do! :-) 16:59:06 And it's written in 100% IsForth. 16:59:28 lol 17:00:31 Isn't that cute? :) 17:00:40 Now I have to add some stuff to it. 17:00:45 But.. it's cute. 17:01:00 You'll include it with IsForth to scare people off, right? 17:01:28 ;) 17:01:34 sif: : fun 5 + . ; 4 fun 17:01:53 mmm... no bot today 17:03:58 Awww... 17:09:50 * Robert wonders how does> is to be implemented. 17:09:55 (In Forth :-) 17:10:20 * Robert checks Moving Forth. 17:22:06 --- join: tathi (~josh@ip68-9-68-50.ri.ri.cox.net) joined #forth 17:22:23 I440r: I code in php.. 17:22:28 that's about the extent of it 17:24:59 lol 17:25:01 teach me :) 17:25:01 * onetom putt-putts roberts shoulder 17:25:06 Hmmm 17:25:06 Hi onetom. 17:25:22 hello, robert 17:25:23 How am I supposed to get the new IP? :-/ 17:25:36 DODOES> IP PUSH RSP 17:25:36 POP hardware call stack TO IP 17:25:36 DATA PUSH PSP NEXT 17:25:44 That's what BYOF says. 17:25:58 im watchin the channel all the time, but i dont have enough time 2 write 2 17:26:09 OK. 17:26:14 I440r: Any ideas? :) 17:27:42 ? 17:27:47 put it on the return stack. 17:27:58 push and pop are GAY word names 17:28:02 use >r and r> 17:28:13 be straight 17:28:15 Put _what_ there? 17:28:48 I440r: I use rpush and rpop internally, to push and pop from the return stack... Anyway, the "dodoes" word has to know where to jump to. 17:28:57 rp@ gets the current return stack pointer address 17:29:06 Er... 17:29:21 That's not what I want. 17:29:22 err a does word CALLS dodoes 17:29:32 Hm.. 17:29:45 OK, there's a special "call" instruction? 17:29:56 Or whatever. 17:30:08 : blah blah ,call thisaddress blah blah ; 17:30:19 colon 'does>', does 17:30:22 dd compile, scode ;compile ;code at the does> location 17:30:24 What does ;code do? 17:30:27 dd ccall, dodoes ;compile a call to dodoes at here 17:30:29 dd exit 17:30:29 the ,call thisaddress compiles a call to the specified address 17:30:40 it pathces the latest created word 17:30:50 ;code and ;uses are difficult to explain ehh 17:30:54 Hehe. 17:31:02 but let me try 17:31:03 What does it change in the header? 17:31:13 NOTHING in the header 17:31:27 first of all you have to realise that ALL isforth words start with some assembler 17:31:33 the header POINTS at that assembler 17:31:37 for a variable the code is 17:31:41 call dovariable 17:31:49 dd body-of-the-variable 17:32:22 the return address of that call is the body field address of the variable 17:32:27 for a colon definition it would be 17:32:29 call nest 17:32:31 dd xxx 17:32:33 dd yyy 17:32:36 dd zzz 17:32:37 dd unnest 17:32:43 OK.. in my Forth, it points either to the body of a word, if it's a high-level word, or the address of a word in IsForth dict. (lowlevel word). 17:33:00 let me show you how ;uses works 17:33:06 variable foo 17:33:12 5 foo ! 17:33:16 ;uses doconstant 17:33:34 ;uses patches the most recent definitions CFA (in this case the cfa of foo) 17:33:40 to USE the specified address 17:34:05 : constant create , ;uses doconstant ; 17:34:10 understand that ? 17:34:32 A word created "constant" calls doconstant, right? 17:34:35 er 17:34:37 created by* 17:35:45 the word created BY constant is patchhed by the ;uses 17:35:50 so if i how say 17:35:52 0 constant blah 17:35:59 the word create creates blah 17:36:06 create ALWAYS creates words as being variables 17:36:17 so the ;uses doconstant CORRECTS that assumption 17:36:33 : : create ;uses nest ] ; 17:36:52 now for ;code 17:36:58 ;code is VERY similar 17:37:04 ] <--- start or turn off compiler? 17:37:16 : [ state off ; 17:37:20 : ] state on ; 17:37:32 lets look at ;code hehe 17:37:37 OK 17:37:41 ;code is an implied UNNEST from any word that uses it 17:37:47 ;uses isnt 17:37:50 you can have 17:38:03 : blah ..... ;uses zyzzy more forth code in here executed by blah ; 17:38:06 if you have 17:38:19 : blah ..... ;code ..... ; 17:38:42 blah execues as far as ;code. everything AFTER ;code is used by the word created by blah 17:38:50 Oh... 17:38:58 immediatly following ;code comes ASSEMBLER code 17:39:06 so you could have a definition that looks like this 17:39:09 : blah 17:39:12 xxx 17:39:13 yyy 17:39:17 zzz 17:39:17 ;code 17:39:21 mov eax, .... 17:39:24 more assembler here 17:39:37 does> calls ;code 17:40:20 the word does> COMPILES a ;code at the point where does> is 17:40:23 so if you have 17:40:29 : constant create , does> @ ; 17:40:35 whats realy compiled is 17:40:37 : constant 17:40:42 create , 17:40:44 ;code 17:40:50 call dodoes 17:40:53 @ ; 17:41:05 so when you run constant 17:41:06 Oh! 17:41:11 you create the new constant 17:41:22 Fuck, that'll be a bitch to implement. 17:42:10 the ;code PATCHES the newly created word to USE the code following the ;code 17:42:14 so all does> words 17:42:18 ALL of them 17:42:30 call a 1 instruction call in the word that created them 17:42:45 Hmmm... 17:42:58 Damn, I might need help to implement this in my Forth. 17:43:03 a constant created by the above definitionm would call the CALL instruction within the word constant 17:43:14 the return address of THAT call is the address of the body of the constant 17:43:15 Or I maybe shouldn't try at 3am 17:43:23 the second call (the one in constant) calls DODOES 17:43:24 3am is a tough one 17:43:37 --- join: Kitanin (~clark@SCF61185.ab.hsia.telus.net) joined #forth 17:43:55 THAT return address is the address of the DOES> part of the word. the high level forth that needs to be interpreted by dodoes 17:43:58 understand ? 17:44:26 I440r: Thanks, I see how it works now :-) You should have some credits for explaning does> to an almost sleeping student, who still understands. 17:44:41 I440r: It's like teachking a monkey physics :P 17:44:47 Yes, I understand. 17:45:05 heh 17:45:14 your a smart(ish) monkey tho :) 17:45:25 monkeys seem to know physics well enough 17:45:43 XeF4: "Don't jump from a cliff, or Gravity will catch you" ? 17:45:58 (at least well enough to reliably swing from tree to tree) 17:46:14 : next ( -- ) 17:46:14 iptr dup cell+ !> iptr @ 17:46:14 header.flags c@ flag-highlevel and 0= if 17:46:14 next-lowlevel 17:46:14 else 17:46:16 next-highlevel 17:46:18 then ; 17:46:24 That's how next looks, heh. 17:46:35 : next-lowlevel ( header -- ) 17:46:35 header.pointer @ nip execute ; 17:46:42 This is how low-level words are called. 17:46:54 erm dont use isforths structure code :P 17:47:06 Now... I don't have _any_ idea how to implement does> 17:47:07 Heh. 17:47:11 I think it's quite OK. 17:47:26 Besides, I'm used to it now. 17:48:23 --- quit: Herkamire ("leaving") 17:48:47 --- quit: XeF4 (Remote closed the connection) 17:49:04 --- join: XeF4 (xef4@lowfidelity.org) joined #forth 17:53:21 Hmm... I think I know how to implement it now. 17:53:26 * Robert will do it tomorrow :P 17:53:32 lol 17:53:43 using does> is easy 17:53:53 it took me YEARS tio unbderstand how it actually worked tho :) 17:54:36 Hehe. 17:54:56 I don't want to waste years, so I bug you and MrReach about it :P 17:55:17 heh 17:55:17 I think I should go to bed now, night. 17:55:35 sov gott 17:56:21 :) 17:56:25 Tackar. 18:25:14 --- quit: Kitanin (Read error: 104 (Connection reset by peer)) 18:32:15 --- quit: skylan (Read error: 104 (Connection reset by peer)) 18:36:16 --- join: skylan (sjh@Riverview78.tbaytel.net) joined #forth 18:38:23 --- quit: I440r ("time to code") 19:17:22 --- join: tcn (tcn@tc4-login6.megatrondata.com) joined #forth 19:21:03 --- quit: tcn (Client Quit) 19:24:46 --- quit: Speuler ("using sirc version 2.211+KSIRC/1.1") 19:26:36 --- quit: skylan (Read error: 104 (Connection reset by peer)) 19:27:26 --- join: skylan (sjh@207.164.213.146) joined #forth 19:49:08 --- join: Herkamire (~jason@ip68-9-58-75.ri.ri.cox.net) joined #forth 21:54:19 --- log: started forth/02.09.27 21:54:19 --- join: clog (nef@206.63.100.249) joined #forth 21:54:19 --- topic: 'All programmers are optimists | x86 Linux Forth coded in asm - http://isforth.clss.net | home of forth - http://www.ultratechnology.com/forth.htm' 21:54:19 --- topic: set by thin on [Sun Sep 15 08:00:43 2002] 21:54:19 --- names: list (clog Robert dmiles Fractal cyberlok Forther TreyB Klaw air onetom skylan Kitanin @ChanServ) 21:54:36 --- join: Herkamire (~jason@68.9.58.75) joined #forth 22:43:33 --- quit: Kitanin (Read error: 104 (Connection reset by peer)) 23:07:39 --- quit: Herkamire ("leaving") 23:33:05 --- quit: skylan (Read error: 104 (Connection reset by peer)) 23:33:36 --- join: skylan (sjh@207.164.213.39) joined #forth 23:59:59 --- log: ended forth/02.09.27