00:00:00 --- log: started forth/17.11.29 00:24:24 reepca: right! well, sorta yeah. i mean the whole overhead of taking stuff from the stack and putting it back on the stack is removed. 00:24:57 reepca: the trade off is thus: (no stack allocation overhead) vs (having to use more transistors) 01:37:58 --- quit: phadthai (Ping timeout: 248 seconds) 01:38:12 --- join: phadthai (mmondor@ginseng.pulsar-zone.net) joined #forth 02:26:55 --- quit: mnemnion (Remote host closed the connection) 02:27:30 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:9d83:baf:ebbd:1af0) joined #forth 02:29:03 --- quit: nighty- (Quit: Disappears in a puff of smoke) 02:30:43 --- quit: proteusguy (Remote host closed the connection) 02:31:50 --- quit: mnemnion (Ping timeout: 246 seconds) 03:03:08 --- join: proteusguy (~proteus-g@2405:9800:bc10:1ca:0:977c:6a76:6644) joined #forth 03:03:08 --- mode: ChanServ set +v proteusguy 03:07:46 hmm what sort of flags would it be? 03:20:04 --- quit: rpcope (Ping timeout: 240 seconds) 03:21:28 --- join: rpcope (~GOTZNC@162.245.217.4) joined #forth 03:28:01 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:9d83:baf:ebbd:1af0) joined #forth 03:33:09 --- quit: mnemnion (Ping timeout: 276 seconds) 04:31:55 --- join: nighty- (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 05:29:12 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:9d83:baf:ebbd:1af0) joined #forth 05:35:21 --- quit: mnemnion (Ping timeout: 276 seconds) 07:28:49 --- quit: MrBusiness (Quit: https://www.youtube.com/watch?v=xIIqYqtR1lY -- Suicide is Painless - Johnny Mandel) 07:31:22 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:9d83:baf:ebbd:1af0) joined #forth 07:35:38 --- quit: mnemnion (Ping timeout: 246 seconds) 08:32:41 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:9d83:baf:ebbd:1af0) joined #forth 08:37:06 --- quit: mnemnion (Ping timeout: 252 seconds) 09:33:14 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:9d83:baf:ebbd:1af0) joined #forth 09:37:34 --- quit: mnemnion (Ping timeout: 240 seconds) 09:48:25 --- join: MrBusiness (~ArcMrBism@2602:306:8325:a300:41ee:1017:b2ad:9e63) joined #forth 10:30:48 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:9d83:baf:ebbd:1af0) joined #forth 11:09:40 hello 11:11:34 --- join: gravicappa (~gravicapp@ppp83-237-166-67.pppoe.mtu-net.ru) joined #forth 11:12:31 I am using gforth, if I run the REPL and type this "-100000 allot" it works but I don't understand whtah gforth actually releases 11:13:08 "works" in what way? 11:13:12 I have allocated nothing before 11:13:17 I don't get an error 11:13:44 it probably knows where the dictionary pointer is initialized and won't let you rewind before that 11:14:00 ok 11:14:15 have you tried writing stuff after you do that? 11:14:30 how I can know where is the dictionary ? 11:14:36 no nothing zy]x[yz 11:14:40 here . 11:17:01 zy]x[yz: look https://pastebin.com/T6KRKLXq 11:18:16 in that case I'd guess you'll start having problems if you begin writing to the dictionary after doing that 11:18:32 I'll try 11:24:36 no error 11:24:51 I didn't mean that you'd see forth throw an error 11:25:04 I meant that you're now writing to memory that doesn't belong to you and who knows what will happen 11:25:22 ok zy]x[yz 11:27:00 just out of curiosity, you might want to try this: here 4096 - 4096 dump 11:27:26 just to see what's in there 11:29:47 thx for the word it's exactly what I need 11:29:57 sure 11:33:35 I think it's gforth.fi the default image file 11:34:13 that would make sense 11:35:01 thx zy]x[yz 12:51:12 --- join: schuldt (~user@50.232.156.226) joined #forth 13:36:54 --- quit: gravicappa (Ping timeout: 248 seconds) 14:07:20 --- quit: Labu (Quit: Leaving.) 14:07:26 --- join: Labu1 (~mik@mvice.pck.nerim.net) joined #forth 14:07:55 --- part: Labu1 left #forth 14:28:50 --- quit: phadthai (Ping timeout: 240 seconds) 14:30:31 --- join: phadthai (mmondor@ginseng.pulsar-zone.net) joined #forth 15:34:54 --- quit: nighty- (Quit: Disappears in a puff of smoke) 15:53:57 --- join: Gromboli (~Gromboli@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 17:19:57 --- join: nighty- (~nighty@kyotolabs.asahinet.com) joined #forth 17:30:55 --- quit: cheater (Remote host closed the connection) 17:31:20 --- join: cheater (~cheater@unaffiliated/cheater) joined #forth 17:35:34 --- quit: cheater (Client Quit) 17:37:43 --- join: cheater (~cheater@unaffiliated/cheater) joined #forth 17:38:22 --- quit: cheater (Client Quit) 17:39:16 --- join: cheater (~cheater@unaffiliated/cheater) joined #forth 18:24:12 "see allot" shows that it checks if the new location is between "usable-dictionary-end" and "forthstart". If you write to the dictionary after doing that allot it will probably clobber some of the system definitions/data. 18:37:04 --- quit: schuldt (Ping timeout: 268 seconds) 21:20:51 --- quit: proteusguy (Remote host closed the connection) 21:38:25 --- quit: Gromboli (Quit: Leaving) 22:32:51 --- join: proteusguy (~proteus-g@14.207.5.13) joined #forth 22:32:51 --- mode: ChanServ set +v proteusguy 23:59:59 --- log: ended forth/17.11.29