00:00:00 --- log: started forth/17.11.10 01:58:10 --- join: karswell (~user@56.28.199.146.dyn.plus.net) joined #forth 02:04:20 --- quit: mnemnion (Remote host closed the connection) 02:05:44 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:f8c7:434c:d7ce:288b) joined #forth 02:11:16 --- quit: mnemnion (Ping timeout: 250 seconds) 02:45:59 --- join: ncv (~neceve@unaffiliated/neceve) joined #forth 03:39:03 --- join: smokeink (~smoke@221.7.252.116) joined #forth 03:39:13 --- quit: smokeink (Remote host closed the connection) 03:39:33 --- join: smokeink (~smoke@221.7.252.113) joined #forth 03:57:23 --- quit: ZombieChicken (Ping timeout: 248 seconds) 03:59:44 --- join: ZombieChicken (~weechat@gateway/tor-sasl/forgottenwizard) joined #forth 04:17:31 --- quit: smokeink (Quit: leaving) 04:26:31 --- quit: nighty- (Quit: Disappears in a puff of smoke) 04:37:45 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:f8c7:434c:d7ce:288b) joined #forth 04:42:30 --- quit: mnemnion (Ping timeout: 252 seconds) 05:22:43 --- join: nighty- (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 05:38:26 --- join: beretta (~beretta@99-47-251-23.lightspeed.clmboh.sbcglobal.net) joined #forth 06:12:43 I had an idea this morning in the shower 06:13:08 I was thinking about machine forth's address register and the fetch/store operators which auto-increment the set address 06:13:44 and also about pointfree's (I think it was his) post a while back about having a here-stack and using , to write to memory 06:14:12 and I came up with this: what if you just had operators which treat the top of the return stack as the machine forth address register 06:15:12 then, you could even get rid of "param". it would just be a r@+ or whatever you'd call it 06:21:01 the only thing is I don't know how those guys were using "a". it wouldn't work if you like to write words that assume it's already been preloaded, because your return address will get in the way. so you'd still write words similarly to classic forth, where addresses are passed on the parameter stack 06:23:42 --- join: nighty-- (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 06:23:56 You're going to implement nearly canonical load/store architecture. You can notice remnants of it in the design even of K580. 06:24:33 I think, it is Intel 8080 or 8085. 06:26:04 --- quit: beretta (Quit: Leaving) 06:29:23 zy]x[yz: I haven't really been liking the C@+ C!+ naming scheme. I think I would like to repurpose , ( comma) to only mean crawling memory access. 8, ( compiles byte from parameter stack to HERE) ,8 ( compiles byte from HERE to parameter stack) 06:35:57 huh. 06:36:04 ,8 is weird 06:47:24 unrelated, in chuck's forths where he called ">r" and "r>" instead "push" and "pop", do you know how he named rdrop, r!, and r@? or did he just omit these words entirely? 06:52:08 --- join: Gromboli (~Gromboli@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 06:57:50 --- quit: nighty-- (Ping timeout: 240 seconds) 07:15:16 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:f8c7:434c:d7ce:288b) joined #forth 07:16:39 --- quit: DGASAU (Ping timeout: 260 seconds) 07:19:48 --- quit: mnemnion (Ping timeout: 252 seconds) 07:37:51 zy]x[yz: he doesn't use those in the 2.0 colorforth blocks as far as I remember 07:38:51 ah, ok 07:48:15 --- join: DGASAU (~user@lmpc.drb.insel.de) joined #forth 08:16:35 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:f8c7:434c:d7ce:288b) joined #forth 08:21:24 --- quit: mnemnion (Ping timeout: 252 seconds) 08:35:50 --- join: DGASAU` (~user@lmpc.drb.insel.de) joined #forth 08:36:57 --- quit: DGASAU (Remote host closed the connection) 08:37:22 --- quit: Keshl (Quit: Konversation terminated!) 08:50:14 --- quit: DGASAU` (Ping timeout: 240 seconds) 09:16:26 --- join: DGASAU (~user@lmpc.drb.insel.de) joined #forth 10:17:46 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:f8c7:434c:d7ce:288b) joined #forth 10:22:15 --- quit: mnemnion (Ping timeout: 258 seconds) 10:27:28 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:f8c7:434c:d7ce:288b) joined #forth 10:30:27 --- quit: impomatic (Ping timeout: 240 seconds) 10:31:14 --- quit: impomatic_ (Ping timeout: 240 seconds) 12:04:45 --- join: gravicappa (~gravicapp@ppp83-237-165-161.pppoe.mtu-net.ru) joined #forth 12:45:58 --- join: Keshl (~Purple@24.115.185.149.res-cmts.gld.ptd.net) joined #forth 12:49:21 --- join: karswell_ (~user@159.92.199.146.dyn.plus.net) joined #forth 12:49:50 --- quit: karswell (Ping timeout: 240 seconds) 12:51:59 --- join: impomatic (~impomatic@host86-191-87-65.range86-191.btcentralplus.com) joined #forth 13:13:59 --- quit: gravicappa (Ping timeout: 248 seconds) 13:34:20 --- quit: ncv (Ping timeout: 264 seconds) 14:21:04 --- quit: bedah (Quit: Ex-Chat) 14:31:50 --- join: Mat4 (~david@ip5b409eae.dynamic.kabel-deutschland.de) joined #forth 14:43:14 --- quit: Mat4 (Quit: leaving) 16:32:24 --- quit: dys (Ping timeout: 248 seconds) 17:05:34 --- quit: zy]x[yz (Ping timeout: 240 seconds) 18:45:23 --- join: Gromboli_ (~Gromboli@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 19:13:04 does anyone here know of a Forth on top of POSIX that can serialize itself into a new ELF binary executable? 19:15:46 --- join: zy]x[yz (~corey@unaffiliated/cmtptr) joined #forth 19:18:22 https://bitbucket.org/bunny351/ff/ looks promising. 19:42:11 --- quit: Gromboli_ (Quit: Leaving) 21:24:53 --- quit: Gromboli (Quit: Leaving) 22:57:12 --- join: dys (~dys@x5f71ff8a.dyn.telefonica.de) joined #forth 23:59:59 --- log: ended forth/17.11.10