00:00:00 --- log: started forth/06.04.22 00:23:17 --- join: NiRev (n=kevin@c-67-182-176-199.hsd1.ca.comcast.net) joined #forth 01:07:01 --- part: NiRev left #forth 02:14:37 --- quit: uiuiuiu (herbert.freenode.net irc.freenode.net) 02:14:37 --- quit: virl (herbert.freenode.net irc.freenode.net) 02:14:38 --- quit: Raystm2 (herbert.freenode.net irc.freenode.net) 02:15:22 --- join: uiuiuiu (i=ian@dslb-084-056-226-143.pools.arcor-ip.net) joined #forth 02:15:22 --- join: virl (n=virl@chello062178085149.1.12.vie.surfer.at) joined #forth 02:15:22 --- join: Raystm2 (n=Raystm2@adsl-68-95-254-38.dsl.rcsntx.swbell.net) joined #forth 02:27:48 --- quit: Quartus (Read error: 104 (Connection reset by peer)) 03:43:25 --- join: Cheery (i=Henri@a81-197-61-21.elisa-laajakaista.fi) joined #forth 04:51:10 --- join: PoppaVic (n=pete@0-2pool236-99.nas22.chicago4.il.us.da.qwest.net) joined #forth 07:15:29 --- quit: PoppaVic ("Pulls the pin...") 07:17:04 --- join: PoppaVic (n=pete@0-1pool67-214.nas22.chicago4.il.us.da.qwest.net) joined #forth 07:34:03 hmm 07:34:54 Usually the outer-interpreter looks at the wl-stack for a work, then tries to convert to a number... 07:35:12 work/word 07:35:37 ...Is this universal? Does this suggest issues? 07:36:18 Above would be "interpret-state". 07:37:25 Is there not a "compile" and even "execute" state where the stack is also examined? 07:38:49 generally the dictionary is searched, then a number conversion attempted, in both states 07:38:55 interpret vs compile seem to be just the iceberg-tip 07:39:02 right. 07:39:27 crc: yer suggesting "the dictionary" based on voclist/wl-lists? 07:39:35 contexts? 07:39:40 that would be implementation dependent 07:39:42 but yes 07:40:06 retro has just one dictionary set up as a linked list, with vocabularies being subchains off of it 07:40:54 right, the "dictionary" should, overall, be nothing more than a tail-list of lists. 07:41:31 it doesn't have to be a list though; it could be an array of hashes, or something else entirely 07:41:35 I've been thinking of integral types. Types, classes, and derivatives. 07:41:58 yeah, I never dick with hashing.. I think of getting there from here. 07:42:35 think of "given this: give me that" 07:47:36 hashing - to me - is akin to CRC.. Taking the CRC and making it work further, and either in a tree or list. hashing and buckets and such are just fillips to a simple "search for this name and return an address" 07:49:07 given sufficient abstraction, I could care less if folks use lists, queues, trees, arrays, or skiplists - whatever. 07:50:42 In fact, such shit may be core - but folks focussing there are not thinking of Forth (or C) for that matter. 07:52:51 I'd suspect they were writing ASM-variants. 08:21:50 --- quit: PoppaVic ("Pulls the pin...") 12:19:40 --- join: snoopy_1711 (i=snoopy_1@dslb-084-058-100-158.pools.arcor-ip.net) joined #forth 12:23:32 --- join: charles` (n=charles`@host-64-139-245-63.nctv.com) joined #forth 12:28:03 --- quit: Snoopy42 (Read error: 145 (Connection timed out)) 15:09:46 --- quit: Cheery ("Leaving") 16:51:29 --- join: NiRev (n=kevin@c-67-182-176-199.hsd1.ca.comcast.net) joined #forth 18:37:45 --- quit: uiuiuiu (Remote closed the connection) 18:37:46 --- join: uiuiuiu (i=ian@dslb-084-056-224-152.pools.arcor-ip.net) joined #forth 21:03:26 --- quit: JasonWoof ("off to bed") 23:16:53 --- join: segher_ (n=segher@dslb-084-056-141-020.pools.arcor-ip.net) joined #forth 23:29:04 --- quit: segher (Read error: 110 (Connection timed out)) 23:59:59 --- log: ended forth/06.04.22