00:00:00 --- log: started forth/02.07.19 01:43:33 --- part: njd left #forth 04:23:32 --- join: cleverdra (julianf@0-1pool37-85.nas2.florence1.sc.us.da.qwest.net) joined #forth 05:02:39 --- join: sif (~sifforth@ip68-14-9-225.ri.ri.cox.net) joined #forth 05:02:40 Type sif: (or /msg sif to play in private) 05:10:03 --- quit: Etaoin (Read error: 110 (Connection timed out)) 05:34:31 --- join: dsmith (dsmith@oh-strongsvillecadent1-1c-245.clvhoh.adelphia.net) joined #forth 05:37:31 --- quit: sif (Read error: 104 (Connection reset by peer)) 05:37:38 --- join: sif (~sifforth@ip68-14-9-225.ri.ri.cox.net) joined #forth 05:37:38 Type sif: (or /msg sif to play in private) 05:39:52 --- quit: sif (Read error: 104 (Connection reset by peer)) 05:39:59 --- join: sif (~sifforth@ip68-14-9-225.ri.ri.cox.net) joined #forth 05:39:59 Type sif: (or /msg sif to play in private) 06:06:49 --- quit: dsmith ("later..") 06:37:09 --- join: Fare (fare@samaris.tunes.org) joined #forth 07:12:50 --- join: Etaoin (~david@ljk25.sat.net) joined #forth 07:12:52 --- join: dsmith (dsmith@oh-strongsvillecadent1-1c-245.clvhoh.adelphia.net) joined #forth 07:17:20 --- quit: dsmith (Client Quit) 08:32:10 --- join: gNoam (xru52729fj@ip5-98.vancbccqac02.dialup.ca.telus.com) joined #forth 08:44:52 --- part: gNoam left #forth 09:12:18 --- join: Herkamire (~jason@wsip68-15-54-54.ri.ri.cox.net) joined #forth 10:05:06 did i440r come on last night? 10:05:31 Hmmm 10:05:34 Haven't seen him. 10:05:54 I don't think he's been here the latest 23 hours. 10:06:17 ah, OK. 10:23:56 --- quit: cleverdra (Read error: 104 (Connection reset by peer)) 10:28:57 --- join: cleverdra (julianf@0-1pool37-85.nas2.florence1.sc.us.da.qwest.net) joined #forth 10:29:24 --- join: tathi (~josh@wsip68-15-54-54.ri.ri.cox.net) joined #forth 10:32:58 Hi tathi :) 10:45:10 --- join: dsmith (dsmith@oh-strongsvillecadent1-1c-245.clvhoh.adelphia.net) joined #forth 10:51:45 ah, but i440r replied to my email. 10:51:49 I guess that I can leave now. 10:51:54 --- quit: cleverdra ("Leaving") 11:01:12 --- quit: Etaoin (Read error: 110 (Connection timed out)) 11:10:38 --- join: XeF4 (waesome@12-245-116-85.client.attbi.com) joined #forth 11:11:00 whose mantra, exactly, is "frequent incremental releases" 11:11:27 Our ;) 11:12:19 --- join: thorin (~puppamelo@212.171.56.34) joined #forth 11:12:30 --- part: thorin left #forth 11:19:27 --- join: Hobart (Hobart@router.jonb.dimensional.com) joined #forth 11:21:35 --- nick: Fare -> FareAway 11:24:26 --- quit: Hobart () 11:32:29 XeF4: it's way better than "good code is written code" 11:32:47 --- join: cleverdra (julianf@0-1pool37-210.nas2.florence1.sc.us.da.qwest.net) joined #forth 11:33:33 Herk: but it's still on par with "disconnect power before servicing" 11:37:04 --- quit: tathi ("leaving") 11:40:48 XeF4: hehe :) 11:41:37 my lobbying for a topic change didn't do anything last time. perhaps we have to wait until futhin comes in and pester him. 11:43:08 does futhin have ops in here, then? 11:44:06 * cleverdra used to have ops, but doesn't remember the password. 11:46:14 --- nick: cleverdra -> ayrnieu 11:47:57 --- nick: ayrnieu -> cleverdra 11:52:18 More people should listen to "good code is written code" ;) 11:52:33 Too much dreaming isn't good. 11:52:45 Dreaming helps, though =) 11:53:34 Well, in small doses it's good. 11:53:50 Only dreams, but no code causes trouble. 11:55:46 hm, I do a lot of dreaming before I program some things. Sometimes I write code, and then stop writing it to continue dreaming. I'm not suggesting this as a production strategy, but sometimes a really good design takes a lot of thought. 11:57:17 Yes. I was refering to projects with only unimplemented ideas. 11:59:48 --- quit: XeF4 ("food") 12:03:54 Robert: I agree that it is good to write code. 12:04:09 Robert: but not that the code written is necesarily good. 12:47:24 --- join: tcn (tcn@tc1-login37.megatrondata.com) joined #forth 12:50:57 --- join: kc5tja (~kc5tja@user-24-214-86-42.knology.net) joined #forth 12:56:04 --- quit: cleverdra (Read error: 110 (Connection timed out)) 12:56:45 --- quit: Herkamire ("leaving") 12:56:49 hey kc 12:57:34 re -- brb -- at work... 13:03:25 --- quit: dsmith ("later..") 13:11:11 --- quit: kc5tja ("THX QSO ES 73 DE KC5TJA/6 CL ES QRT AR SK") 14:22:27 --- quit: Soap- (Read error: 104 (Connection reset by peer)) 14:41:17 --- join: dsmith (dsmith@oh-strongsvillecadent1-1c-245.clvhoh.adelphia.net) joined #forth 14:57:11 --- quit: tcn (Read error: 110 (Connection timed out)) 15:17:34 --- join: tcn (tcn@tc4-login3.megatrondata.com) joined #forth 15:31:29 --- quit: dsmith ("later..") 15:52:30 --- quit: tcn ("Leaving") 16:01:24 --- join: Soap` (~flop@202-0-42-22.cable.paradise.net.nz) joined #forth 16:05:07 --- join: dsmith (dsmith@oh-strongsvillecadent1-1c-245.clvhoh.adelphia.net) joined #forth 16:13:51 --- join: kc5tja (~kc5tja@ip68-7-162-51.sd.sd.cox.net) joined #forth 16:14:35 --- quit: dsmith ("later..") 16:56:50 --- join: Etaoin (~david@ljk26.sat.net) joined #forth 17:10:06 --- join: I440r (mark4@1Cust96.tnt1.bloomington.in.da.uu.net) joined #forth 17:33:22 Hey. 17:35:06 I440r: In IsForth, you're using several vocabularies, but how does one vocabulary differ from another? 17:40:56 --- join: dsmith (dsmith@oh-strongsvillecadent1-1c-245.clvhoh.adelphia.net) joined #forth 17:42:02 what do you mean 17:42:06 how does it differ 17:42:29 do you understand how vocabularies work ? 17:42:33 if not ill explain 17:42:35 its very simple 17:42:37 sort of hehe 17:43:06 Thanks :) 17:43:11 Well 17:43:21 In my forth I had ONE dictionary pointer. 17:43:38 ok first of all, as you know word headers are chained together\ 17:43:47 Why have more, how to switch etc.? 17:43:52 a vocabulary in its simplest form could be 17:43:53 Yeah. 17:44:00 some_voc: 17:44:03 call dovoc 17:44:11 dd pointer_to_last_word_in_chain 17:44:28 dovoc adds this vocabulary to context 17:44:32 context is an array of vocabularies 17:44:41 FIND only searches vocabularies taht are in context 17:44:59 new definitions go into the vocabulary stored in teh variable "current" 17:45:12 isforths vocabularies are slightly more complex 17:45:25 each vocabulary is an array of "last word in chain" 17:45:33 64 chains per vocabulary to be exact 17:45:48 when a word is created one has to decide which chain of the vocabulary to attach it to 17:46:01 to do this you calculate a hash value for teh word name 17:46:24 when you search for a word you also use the words hash to decide which chain to search 17:46:29 this speeds up teh search alot 17:46:42 Yeah.. but how are the different vocabs used? 17:46:42 because, instead of one HUGE chain you have lots of little chains 17:46:59 well. the primary vocabulary is "forth" 17:47:04 you can also have "assembler" 17:47:20 the assembler vocabulary is only used when you are compiling CODED definitions 17:47:39 Why have more than one? 17:48:01 And, when a word is looked up, are all vocabs searched? 17:51:43 no. only the ones that are in context 17:51:55 Uhm 17:51:58 when you execute a vocabulary that vocab is added to the context stack 17:52:04 What's the point of that? 17:52:21 ok. theres a word in forth called "and" 17:52:26 theres a word in assembler called "and" 17:52:40 if both forth and assembler were always in context we would always get only one of them 17:52:53 which one we want depends on "context" hehe 17:52:56 Oh, I see. 17:53:05 What's the context stack? 17:53:13 the assembler "and" only has meaning when we are trying to assemble the "and" instruction 17:53:16 How is it designed? 17:53:32 an array of vocabs 17:54:19 ok. "context manipulation words" 17:54:30 only - removes all words from context except ROOT 17:54:51 when you create a new vocabulary the vocabulary word is compiled into the ROOT vocabulary 17:54:56 vocabulary foo 17:55:10 if you do that, the root vocabulary will gain a new word called foo 17:55:26 when you execute foo the FOO vocabulary is added to context 17:55:29 you often see 17:55:34 only forth also definitions 17:55:41 isforth doesnt use the word "also 17:55:48 its a noop in isforth 17:56:02 do u have isforth handy ? 17:56:05 do 17:56:07 ./isforth 17:56:08 Yeah 17:56:11 .context 17:56:21 dot context shows what voabs are in context 17:56:30 .vocabs says what vocabularies are defined 17:56:35 so if you do 17:56:39 only .context 17:56:41 you will get 17:56:43 ROOT 17:56:46 nothing else 17:56:50 only forth .context 17:57:00 ROOT FORTH <-- top of context stack is to the right 17:57:21 so. if you now say "foo" forth will search the FORTH vocabulary and if foo is not found it will search the root vocabulary 17:57:27 now do 17:57:39 only forth compiler terminal .context 17:57:56 forth compiler terminal 17:58:00 now do.... forth 17:58:08 you wont get 17:58:13 forth compiler terminal forth 17:58:17 you wont have forth in there twice 17:58:31 what happens is "forth" gets pulled up to the top of the context stack so you get 17:58:39 compiler terminal forth <-- top 17:59:05 thats different to other forths 17:59:06 if you do 17:59:14 only forth also also also also also 17:59:15 you get 17:59:21 root forth forth forth forth forth 17:59:25 which is DUMB!!!!!!!!!!!!!!!! 17:59:41 the word "also" is a context stack dup 17:59:54 the word previous is a context stack drop 18:00:08 theres also a realy nice word called "seal" 18:00:27 you can create a "application" vocab and have IT be the only one in context 18:00:42 only application root previous 18:00:46 that would do the same thing 18:00:53 understand that ? 18:01:07 If I do that, can I use other vocab's words? 18:01:16 no 18:01:28 you are SEALED into ONE vocabulary 18:01:40 however. isforth allows you to seal into MULTIPLE vocabularies 18:01:57 only voc1 voc2 root previous 18:02:19 voc1 and voc2 words can still CALL words in teh other vocabularies but you cannot execute them interactivly 18:02:24 onlt root previous 18:02:35 Now. context doesn't print anything. 18:02:48 if you do that you have NO vocabularies in context hehe 18:02:58 Oh, hehe 18:02:59 you just locked yourself out of ALL vocabularies hehe 18:03:12 actually. doing that is the same as doing 18:03:16 only previous 18:03:39 and the sources (isforth/forthsrc/vocabs.f) tells you not to do that heh 18:04:36 :D 18:04:45 dup gave me a segfault then :) 18:05:17 no. the search for dup did 18:05:20 hehe 18:05:50 Well, I was thinking about writing a little Forth system. 18:05:59 :) 18:05:59 Non-bloatware ;) 18:06:15 So, figured I had to learn a little bit more about the internals. 18:06:29 Guess I'll "borrow" significant parts from IsForth. 18:06:59 But that's what the GPL family licenses are for, isn't it? ;) 18:07:20 thats what isforth is for, so lame.... erm beginners can learn forth 18:07:27 hehe 18:08:02 BAH! 18:08:09 * Robert hides in his lamer corner. 18:08:33 heh 18:08:37 your not a lamer 18:08:53 i dont equate "not knowing YET" with "dumbass" like SOME people on irc doe 18:08:54 do 18:09:16 That's good :) 18:09:23 I try to do the same. 18:09:44 A lot of people ARE dumbasses, though :/ 18:09:57 Asking stupid questions and not caring for the answers. 18:11:11 --- join: tcn (tcn@tc2-login35.megatrondata.com) joined #forth 18:11:15 :) 18:11:19 tcn! 18:11:20 boo :) 18:11:21 hey 18:11:21 Hey tcn 18:11:28 whers my assembler ;) 18:11:29 heh 18:11:32 IsForth asembler done yet? 18:11:36 hahaha 18:11:39 assembler* 18:12:07 were ganging up on you - 18:12:10 tag team :) 18:12:29 we should all make him feel GUILTY for not having finished it yet :P 18:12:35 Yeah. 18:12:50 He doesn't care enough about us :( 18:13:00 *sniff* 18:13:09 tcn - you messed with the latest isforth yet ? 18:13:18 im almost ready to release 1.09b 18:13:28 Cool, what's new in it? 18:13:56 allocate, deallocate 18:14:01 modified structs a little 18:14:02 Wow :) 18:14:05 might need that. 18:14:21 want to get dns queries working and add my sockets stuff 18:14:39 DNS still not working 18:14:41 ? 18:14:42 hey, what modutils do I need for linux 2.2.20? 18:15:34 rob i havent touched teh sockets stuff in a while 18:15:46 the alloc/dealloc was needed anyway :) 18:15:51 Yeah. 18:16:13 Now I can really start using Forth ;) 18:17:30 oh - and it will have the new windowing code in it 18:17:40 still havent coded pull down menus tho 18:18:15 Editor+ 18:18:16 ? 18:18:30 ? 18:18:42 Do you have any editor? 18:18:54 I use vi now, but it's not written in Forth ;) 18:19:56 i use joe 18:20:02 --- join: dsmith_ (dsmith@oh-strongsvillecadent1-1c-245.clvhoh.adelphia.net) joined #forth 18:20:11 i think isforth will look at the $EDITOR env var and shell out to it 18:20:13 --- quit: dsmith_ (Remote closed the connection) 18:20:25 might one day write a SANE editor for unix 18:20:26 * tcn is writing an editor 18:21:17 tcn: Nice :) 18:21:55 Then you have 2 things to feel guilty about. 18:21:56 bah - it wont be sane. he isnt sane ennuff himself :P 18:22:08 ;) 18:22:15 * tcn nods 18:22:38 to prove your point, it has tables & hyperlinks 18:23:11 lol 18:23:47 but i want it to do code too 18:24:31 ^L...^@ is a link, ^T...^@ is a table.. :) 18:24:51 so I could embed that in the code.. 18:25:08 ^@ = Ctrl-2 ? 18:25:12 null 18:25:30 Hmm 18:25:50 ^@ is a zero 18:25:57 0x00 18:26:18 joe lets you embed any character into your source 18:26:22 Well, on a keyboard, how to make that? 18:26:25 escape ` 0x00 18:26:30 embedds a zero char into the source file heh 18:27:29 yea, i use joe right now :) 18:27:39 `@ will do it 18:28:41 anyway, the tables work nice.. i've got alternative background colors so you can tell the rows apart.. 18:28:50 i mean, alternating 18:29:52 cool :) 18:30:01 i bet its not written in isforth tho :P 18:30:01 bleh 18:30:10 C 18:31:37 --- part: kc5tja left #forth 18:35:34 --- quit: dsmith (Remote closed the connection) 18:35:43 god damn it, they don't make it easy to find the right modutils version.. 18:36:15 fucking linux piece of shit :) 18:37:57 lol 18:38:05 just install debian :P 18:39:22 no way.. the one i put together works great 18:40:31 nice and organized.. nothing more than 2 directories deep.. 18:40:47 lynxcgi manpages. 18:40:55 woo hoo debian 3.0 released :) 18:45:16 like hell i'm gonna run that 18:45:46 i'm gonna stick with the 2.2 kernel until I write my own OS :) 18:46:09 lol 18:48:40 i downloaded "linux-lite", haven't looked at it yet 18:49:34 i got a contract, ive been doing alot of RTFM here 18:51:23 cool 19:02:19 --- join: TheBlueWizard (TheBlueWiz@ip-216-25-202-54.vienna.va.fcc.net) joined #forth 19:02:24 hiya all 19:02:36 and hiya I440r in particular :) 19:03:17 hehe 19:03:20 i got a contract - did i tell you ? 19:04:33 yeah, you told me :) did you get another contract that lets you work at home? 19:04:55 yes but i work on site next month 19:05:09 ive gotta do some reverse engineering now too :) 19:05:21 soon as i get teh hardware i have to RE teh roms 19:06:21 cool, and ouch....I have some experience with RE (pointing to RE'ing Apple ][ ROMs and C-64 ROMs, among few others) 19:08:02 hehe i have a very very useful tool here tho 19:08:11 the interactive disasembler PRO 19:08:18 i paid for it hehe 19:08:20 and this is just 8051 :) 19:08:36 ah...IDA Pro....never played with it.... 19:09:18 its only the best reverse engineering tool ever devised 19:09:22 literally 19:10:26 yeah...and I wish there is a Free Software version of that! When I'm done with my two other projects, I hope I will develop 6502 interactive disassembler.... 19:11:05 im gona do an 8051 one 19:11:24 i had it started already but i abandoned it, i got the disassebmbler part of it ported already hehe 19:11:33 its going to be able to execute teh code too tho 19:12:07 hehe...you already have a 8051 disassembler...it'd be cool to see an interactive version...but it's a lot of work....by the way, is 1.09b out? 19:12:53 not yet, got a cpl of things i want to finish first 19:13:32 * TheBlueWizard nods....good things to close the book on project XYZ, as always 19:14:29 i have a few things left hanging heh 19:15:50 hehe 19:26:01 now that woody is out, I plan to ask my friend in upstate to burn a dozen CDs for me :) (if he can do that...since he is working as a contractor and lives in another city) 19:26:44 heh 19:27:27 heh re: your quip on #debian re: X 4.1 19:27:56 heh 19:28:25 somenbody musta upgraded it while i wasnt looking :P 19:28:38 he 19:28:45 lol...yeah right! 19:29:48 The only thing that's changed is that Woody is called stable now, right? 19:30:20 Soap`: woody is released! 19:30:33 and yes, it is now stable 19:33:03 Groovy. 19:33:20 absolutely! 19:34:52 now...CD burning....hehe....since I have slow connection, have to have someone burn it for me, since I wanna install it on as many roaches^H^H^H^H^H^H^Hcomputers as possible :) 19:35:26 wasn't woody supposed to be done 3 years ago? 19:35:26 hehe 19:36:25 ha ha ha....potato was release 2 and a half years ago....tcn, you better wake up and read some more! :) 19:38:13 --- nick: FareAway -> Fare 19:38:23 hiya Fare 19:38:35 hi fare 19:40:56 hey fare, what's new? 19:47:43 --- join: dsmith (dsmith@oh-strongsvillecadent1-1c-245.clvhoh.adelphia.net) joined #forth 19:47:56 hiya dsmith 19:48:31 evnin 19:49:06 --- join: njd (~junk@njd.paradise.net.nz) joined #forth 19:58:03 --- quit: tcn ("Leaving") 20:26:38 --- quit: dsmith (Remote closed the connection) 20:33:13 --- quit: njd ("brb") 20:37:15 --- join: njd (junk@njd.paradise.net.nz) joined #forth 20:37:38 hiya njd 20:38:40 hii 20:38:46 njd 20:38:50 whassup? 20:39:14 updating debian to 3.0 20:39:15 how much memory do you have installed 20:39:17 what about u 20:39:26 I440r who u talking too 20:39:34 you 20:39:42 228mb 20:40:08 me...vegging out, surfing the Net, etc....need to veg out after today's rather stressful and somewhat disastrous day 20:40:13 im not sure if a swap file over 64 meg will all be used 20:40:26 but you can have multiple swap partitions 20:40:40 well 20:40:47 i dunno how big my swap is 20:41:18 oi i440r dist-upgrade 20:41:21 isnt upgrading 20:41:22 heh 20:41:35 dist-upgrade from woody to woody ? 20:41:36 lol 20:41:38 no 20:41:41 im on unstable 20:41:46 i changed my sources.list 20:41:54 apt-get update 20:42:01 and it wont do the next part 20:42:11 you can't downgrade 20:42:27 eh 20:42:32 its all your fault i440r 20:42:56 ill do an upgrade then 20:43:08 bleh does the same 20:43:08 oh well 20:43:35 quick fix I berlieve is to have it explicityly point to sarge....but check with some who *knows* things first! 20:44:04 I am assuming sarge is same as sid at this time 20:44:14 I could be totally wrong 20:46:55 --- quit: njd ("brb") 20:48:49 --- join: njd (junk@njd.paradise.net.nz) joined #forth 20:49:00 my god this wmaker theme is terrible 20:54:56 --- nick: Fare -> Fare3153 20:56:40 --- quit: I440r (Read error: 104 (Connection reset by peer)) 21:04:00 --- join: I440r (mark4@1Cust96.tnt1.bloomington.in.da.uu.net) joined #forth 21:04:24 hiya I440r the great IsForth coder! ;) 21:05:06 not so great or i would have an assembler by now :P 21:05:28 lol....got it...still stuck on it? 21:08:04 not yes but..... HELL yes! 21:08:25 lol 21:09:25 I know you want what amount to a NASM clone (e.g. normal assembler syntax, labels, etc, not Forth style syntax) 21:10:47 forth syntax sux big time except for forth 21:10:50 for assembler it sux 21:13:44 hehe....there are tradeoffs involved....for short snippets I think Forth syntax is quite fine for assembly...but for long code section of assembly language, Forth syntax can drive many batty :) 21:18:30 --- quit: I440r (Read error: 104 (Connection reset by peer)) 21:21:32 --- quit: Fare3153 (Read error: 113 (No route to host)) 21:24:17 junk@njd:~/bubblemon-dockapp-1.4$ make 21:24:17 gcc -O3 -ansi -Wall `gtk-config --cflags` -DENABLE_DUCK -DENABLE_CPU -DENABLE_MEMSCREEN -c -o bubblemon.o bubblemon.c 21:24:17 sh: gtk-config: command not found 21:24:21 what .deb is gtk-config in ? 21:26:03 beats me....I currently only run console Debian machine....when I get a woody CD set, I plan to build a X windows machine 21:26:22 * TheBlueWizard has a lot to learn :) 21:27:14 console :o 21:28:51 yep 21:29:24 I installed slink straight off the Net 2 and a half years ago 21:30:14 slink? 21:30:49 the one before potato 21:33:13 ohh 21:33:13 ok 21:41:40 gotta go...bye all 21:41:59 later 21:42:13 bye njd 21:42:19 --- part: TheBlueWizard left #forth 23:37:39 --- quit: njd ("Client Exiting") 23:59:59 --- log: ended forth/02.07.19