00:00:00 --- log: started forth/17.02.18 00:36:46 pointfree: haven't checked. will do, thank you 01:32:27 --- quit: mnemnion (Remote host closed the connection) 03:06:11 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 03:10:44 --- quit: mnemnion (Ping timeout: 268 seconds) 03:17:00 --- join: GeDaMo (~GeDaMo@212.225.112.221) joined #forth 04:13:38 --- join: wa5qjh (~Thunderbi@121.54.90.157) joined #forth 04:35:16 --- join: john_cephalopoda (~john@unaffiliated/john-minetest/x-5335115) joined #forth 04:38:34 --- join: gravicappa (~gravicapp@ppp83-237-165-240.pppoe.mtu-net.ru) joined #forth 04:54:31 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 04:58:54 --- quit: mnemnion (Ping timeout: 260 seconds) 05:47:05 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 05:51:12 --- quit: mnemnion (Ping timeout: 240 seconds) 06:13:39 --- quit: karswell` (Remote host closed the connection) 06:15:02 --- join: karswell` (~user@21.208.208.46.dyn.plus.net) joined #forth 07:28:57 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 07:57:00 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 08:01:00 --- quit: mnemnion (Ping timeout: 240 seconds) 08:05:27 --- join: dual (~bonafide@subzeroup.core.rzwireless.net) joined #forth 09:17:37 --- quit: karswell` (Remote host closed the connection) 09:19:01 --- join: karswell` (~user@21.208.208.46.dyn.plus.net) joined #forth 10:05:47 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 10:05:59 --- join: gnooth (~gnooth@2602:306:cf96:8b60:b4ab:fe4e:1c51:b0d9) joined #forth 10:08:19 --- quit: gravicappa (Ping timeout: 240 seconds) 10:10:30 --- quit: mnemnion (Ping timeout: 260 seconds) 10:21:52 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 10:53:55 I bought the 3rd to last copy of "Footsteps in an Empty Valley" from Ting. It's in a plastic sleeve on my coffee table. Now, a new edition with updated graphics etc was just released: https://www.amazon.co.uk/dp/B06X6JGM5L 10:54:12 (as an ebook) 11:18:01 --- join: Keshl (~Purple@24.115.181.94.res-cmts.gld.ptd.net) joined #forth 11:18:40 --- join: ACE_Recliner (~ACE_Recli@c-50-165-178-74.hsd1.in.comcast.net) joined #forth 11:38:37 "Systems Guide to fig-Forth" by Ting from 1986 https://docs.google.com/file/d/0B_gErHTyKbpNSUxHUEd1bjluMUk/edit 11:41:33 --- quit: nerfur` (Read error: Connection reset by peer) 11:42:33 --- join: nerfur (~nerfur@mail.freeside.ru) joined #forth 12:29:40 --- join: rgrinberg (~rgrinberg@24-246-56-85.cable.teksavvy.com) joined #forth 12:32:48 --- quit: impomatic (Ping timeout: 276 seconds) 12:39:38 --- quit: neceve (Quit: Konversation terminated!) 12:46:39 --- join: mnemnia (~mnemnion@2601:643:8102:7c95:69b5:248c:70aa:9ba7) joined #forth 12:49:38 --- quit: mnemnion (Ping timeout: 260 seconds) 13:41:51 --- quit: real-grue (Read error: Connection reset by peer) 13:41:51 --- quit: true-grue (Read error: Connection reset by peer) 13:55:55 thx 14:05:14 --- quit: GeDaMo (Remote host closed the connection) 14:11:03 --- quit: Zarutian (Quit: Zarutian) 14:30:39 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 14:31:12 --- quit: Zarutian (Read error: Connection reset by peer) 14:31:39 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 14:47:34 --- quit: gnooth (Quit: Leaving) 15:01:14 what's your guys' opinion about having pad rotate between four or eight fixed scratch pad areas? 15:01:41 maybe I'm using it wrong but occasionally I have problems with pad collisions 15:52:50 zy]x[yz: I personally don't get PAD collisions myself. PAD is typically not a fixed location. PAD is typically defined as : PAD HERE 400 + ; ( or something similar) 15:52:58 I like to say that C, is a special case of C!+ for the dictionary, how about a C, with the same name but for the PAD. (If you're still getting PAD collisions) 15:58:39 --- quit: ACE_Recliner (Remote host closed the connection) 15:58:58 As it is typically defined, the PAD address is advanced when the dictionary pointer is advanced. This is usually what you want if you compile the contents of the PAD to the dictionary shortly thereafter. 16:25:32 it's mostly string manipulation. I use the pad to build up strings, which means you can never use two string-building words in a higher order string-building word 16:26:30 I wrote my little pad rotator idea and it works just fine. I wonder if I'm toing to regret it down the road though when it generates some weird bug that's hard to figure out 17:33:50 --- join: beretta (~beretta@99-99-119-146.lightspeed.bcvloh.sbcglobal.net) joined #forth 17:37:38 Is there a reason just ALLOTing and then un-ALLOTing wouldn't work? 17:38:19 (I suppose I'm not quite understanding the kinds of problems that string manipulations involve) 17:40:08 ALLOT is designed for static allocation... not meant to be freed 17:40:48 I'm sure there's tons of different implementations of ALLOT, but, in short, it usualyl works like just another stack (of code/data) 17:42:37 I know, but I don't see why, for example, in the case of concatenating strings, you couldn't just allot some more memory to hold the result. As long as you get rid of it in the same order as you got it, it works fine 17:45:05 yup. I agree. 17:45:46 I suppose there are probably some cases where it really sucks that the dictionary is treated like a stack but doesn't have stack manipulation operators (nor would they be feasible, I imagine) 17:46:37 "feasible" meaning "no point to doing it", not "can't be done". Not sure which of those two is technically correct. 17:52:13 er... "not feasible" meaning that. 17:54:04 gotcha. 17:54:33 nothing says the dictionary headers, code and data have to be interleaved. 17:55:38 I ususally like to keep my headers separate from the code/data "stack"... that way I can dispose of the header when the application is done. 17:56:47 How do you do that? Have dictionary headers grow from one end and have code/dat grow from another end? 17:58:10 well... sometimes. 17:58:41 one time I put the headers in a totally different address space... to maximize code/data area 17:59:16 don't have to do that though. 18:00:48 but usually, my headers grow upwards, just like my code/data... just in a different section/area 18:03:15 I've leaned toward VM's that have several such sections/stacks... input source stack, data stack, return stack, code stack, dictionary stack, etc... 18:13:20 --- quit: wa5qjh (Remote host closed the connection) 18:16:16 --- join: wa5qjh (~Thunderbi@121.54.90.157) joined #forth 18:19:17 maybe I need a text stack 18:19:51 I've heard reference made to "string stacks" before 18:53:04 --- quit: Zarutian (Quit: Zarutian) 19:16:10 --- quit: john_cephalopoda (Remote host closed the connection) 19:26:41 --- quit: rgrinberg (Ping timeout: 240 seconds) 19:37:22 --- join: vsg1990 (~vsg1990@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 19:39:24 --- quit: vsg1990 (Client Quit) 19:43:33 --- join: vsg1990 (~vsg1990@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 19:48:43 --- quit: dual (Read error: Connection reset by peer) 19:52:41 --- join: dual (~bonafide@subzeroup.core.rzwireless.net) joined #forth 19:53:37 --- join: ACE_Recliner (~ACE_Recli@c-50-165-178-74.hsd1.in.comcast.net) joined #forth 20:00:37 --- quit: beretta (Quit: Leaving) 20:03:22 --- join: fiddlerwoaroof (~fiddlerwo@unaffiliated/fiddlerwoaroof) joined #forth 20:57:28 --- join: IRCFrEAK (~gk.1wm.su@2a03:4a80:2:2d3:2d3:9c14:a427:77be) joined #forth 20:57:30 --- part: IRCFrEAK left #forth 21:08:31 --- join: neceve (~ncv@unaffiliated/neceve) joined #forth 21:31:03 --- quit: APic (Ping timeout: 258 seconds) 21:43:49 --- join: APic (apic@apic.name) joined #forth 22:33:33 --- quit: ACE_Recliner (Remote host closed the connection) 23:30:33 --- join: true-grue (~true-grue@176.14.222.10) joined #forth 23:34:52 --- quit: vsg1990 (Quit: Leaving) 23:37:32 --- quit: proteusguy (Ping timeout: 240 seconds) 23:43:38 --- quit: MrBusiness (Ping timeout: 245 seconds) 23:55:29 --- join: gravicappa (~gravicapp@ppp83-237-161-204.pppoe.mtu-net.ru) joined #forth 23:59:59 --- log: ended forth/17.02.18