00:00:00 --- log: started retro/06.10.28 01:05:36 --- join: Cheery (n=Cheery@a81-197-19-23.elisa-laajakaista.fi) joined #retro 01:19:12 --- quit: Cheery (Remote closed the connection) 02:01:00 --- join: Cheery (n=Cheery@a81-197-19-23.elisa-laajakaista.fi) joined #retro 02:15:39 --- quit: Cheery (Remote closed the connection) 02:24:05 --- join: Cheery (n=Cheery@a81-197-19-23.elisa-laajakaista.fi) joined #retro 03:35:29 --- quit: virl (Read error: 104 (Connection reset by peer)) 03:57:46 Imagine two forth systems over each other, having different words, how should one handle this? 05:22:27 --- join: erider (n=erider@unaffiliated/erider) joined #retro 06:44:38 --- join: virl (n=virl@chello062178085149.1.12.vie.surfer.at) joined #retro 07:57:11 Quartus, your interpreted conditionals are incredible. 07:57:21 When I actually read what they do. ;) 07:57:54 It's cool how you dismount the parser. 08:03:55 --- join: virl_ (n=virl@62.178.85.149) joined #retro 08:04:18 --- quit: virl (Read error: 110 (Connection timed out)) 08:07:44 --- join: snoopy_1711 (i=snoopy_1@dslb-084-058-147-073.pools.arcor-ip.net) joined #retro 08:08:47 hi snoopy_1711 how are you? 08:18:14 --- join: Raystm2 (n=NanRay@adsl-69-149-60-46.dsl.rcsntx.swbell.net) joined #retro 08:24:39 --- quit: Snoopy42 (Read error: 110 (Connection timed out)) 08:24:46 --- nick: snoopy_1711 -> Snoopy42 08:43:05 --- quit: virl_ (Read error: 110 (Connection timed out)) 09:40:04 --- quit: erider (Read error: 110 (Connection timed out)) 09:53:52 --- log: started retro/06.10.28 09:53:52 --- join: clog (n=nef@bespin.org) joined #retro 09:53:52 --- topic: 'RetroForth | Pastebin @ http://retroforth.net/paste | The editing key is 'despair'' 09:53:52 --- topic: set by crc on [Sat Aug 05 13:13:30 2006] 09:53:52 --- names: list (clog Raystm2 Snoopy42 Cheery neceve_ timlarson @crc Quartus nighty @ChanServ @lukeparrish) 09:57:06 --- join: erider (n=erider@unaffiliated/erider) joined #retro 10:10:14 --- join: forther (n=forther@c-67-180-209-27.hsd1.ca.comcast.net) joined #retro 12:40:44 --- log: started retro/06.10.28 12:40:44 --- join: clog (n=nef@bespin.org) joined #retro 12:40:44 --- topic: 'RetroForth | Pastebin @ http://retroforth.net/paste | The editing key is 'despair'' 12:40:44 --- topic: set by crc on [Sat Aug 05 13:13:30 2006] 12:40:44 --- names: list (clog erider @Raystm2 Snoopy42 Cheery neceve_ timlarson @lukeparrish @ChanServ nighty Quartus @crc) 12:42:09 Quartus: yes they are when you end up with a whole big system where different rules must be toggled on and off. 12:42:48 Cheery, are you speaking from experience, or projecting some theoretical system wherein you anticipate a lot of naming conflicts? 12:43:08 lukeparrish: fixed 12:44:04 Quartus: from recent experience, there may be an another vector which forces the usage of only one wordlist which I've not yet noticed. 12:44:28 I'm not sure I understand quite what it is your facing, but you can certainly choose to search only one wordlist. 12:44:33 No, wordlists aren't for anticipating with naming conflicts. 12:45:06 They are used for structuring the information and tags for human memory. 12:45:35 ie. You notice you have very hard to remember thousands of words, even many times you remember more than that. 12:45:44 In form of small complete systems. 12:46:35 In fact I work with a module system that lets me reveal only the public words of any given lexicon, keeping the others in module-specific private wordlists. This hugely cuts down on the number of names I have to consider, from an application-development standpoint. 12:47:15 It also takes away the worry that a given private word will step on the name of another module's public or private words. 12:47:31 Raystm2: tunes is back up now; it was having a hard drive replaced this morning 12:48:46 My goal is not that. Ie. In my proposed wordlist system, you'd have complete set of tools in each wordlist which you would apply to use, possibly merge with another toolsets which has no tools for same use (same name), handle them like you'd handle your woodwork tools. 12:50:53 You can do that with the Standard wordlist system, if you choose -- placing each group of words, or module, into its own wordlist. I'm not sure there's any advantage. 12:52:44 yep, you must break and reassemble the forth system first to apply this. 12:54:01 If you want to subdivide the existing wordlists of a system, in most systems you'd simply alias the words into new wordlists. 12:54:25 I do this for testing my code for portability -- seal off all words except the Standard ones. 12:55:39 I do this in the ANS layer for retro -- I move a handful of words into their own wordlist, down near the bottom. 12:55:54 Ah, I mean you must break the whole system, even disassemble the words into one big chunk and assemble it back. 12:56:04 :) 12:56:16 You don't need to do that in order to rearrange words into discrete wordlists. 12:56:43 --- join: Quartus_ (n=Quartus_@209.167.5.1) joined #retro 12:58:03 yep, but to study and reorder it all into more usable nodes would be useful. 13:09:45 It should be learned in groups, certainly. I'm not sure subdividing it so as to require each group to be specially accessed would be anything but a hindrance, for public words. 13:24:09 good night Quartus_, I'm going to sleep now. Lets talk tomorrow more. 13:24:56 --- quit: Cheery ("Download Gaim: http://gaim.sourceforge.net/") 15:28:49 --- join: virl (n=virl@chello062178085149.1.12.vie.surfer.at) joined #retro 16:21:08 Hey. 16:54:31 hey 17:22:50 --- join: jas2o (n=jas2o@WNPP-p-203-54-36-184.prem.tmns.net.au) joined #retro 17:27:56 --- join: forther (n=forther@c-67-180-209-27.hsd1.ca.comcast.net) joined #retro 17:59:45 --- part: forther left #retro 18:08:52 --- quit: jas2o ("Chatzilla 0.9.74 [XULRunner 1.8.0.1/2006012608]") 21:27:56 --- join: nighty_ (n=nighty@sushi.rural-networks.com) joined #retro 22:37:45 --- quit: erider ("I don't sleep because sleep is the cousin of death!") 23:45:43 --- quit: Quartus (Read error: 104 (Connection reset by peer)) 23:59:59 --- log: ended retro/06.10.28