00:00:00 --- log: started forth/09.06.22 00:49:03 --- quit: tathi (Read error: 60 (Operation timed out)) 01:31:18 --- part: X-Scale left #forth 02:25:10 --- join: thom_ (n=thom@pool-173-51-224-238.lsanca.fios.verizon.net) joined #forth 02:25:38 anyone know anything about the call/cc words? 02:31:15 --- join: GeDaMo (n=gedamo@212.225.115.246) joined #forth 02:39:28 --- join: proteusguy__ (n=proteusg@61.7.144.97) joined #forth 02:41:07 --- quit: proteusguy_ (Read error: 110 (Connection timed out)) 04:49:33 --- quit: nighty__ (Remote closed the connection) 05:09:08 --- join: tathi (n=josh@dsl-216-227-91-166.fairpoint.net) joined #forth 05:10:30 what call/cc words? 05:17:38 Factor probably has such a thing, but off the top of my head I don't know of a Forth that has actual continuations. 05:18:21 Actually I'm not sure how that would work, since things in Forth are usually early bound and you don't really do dynamic scoping much, if at all. 05:19:19 --- quit: GeDaMo ("Leaving.") 05:19:36 I was thinking there should be a simple call/cc in forth - just to put a copy of the return stack somewhere 05:38:45 --- quit: TreyB (Read error: 113 (No route to host)) 06:09:29 Ah. Yeah, you could certainly do that. 06:09:49 That's the thing I've never understood about continuations -- what data do they save, and what do they ignore? 06:17:39 save the stack and program counter. ignore the heap/dictionary 06:18:08 (return stack contents, not just a pointer) 07:38:53 --- nick: proteusguy__ -> proteusguy 07:52:11 --- join: TreyB (n=trey@74.203.168.157) joined #forth 08:15:46 --- join: kar8nga (n=kar8nga@a-226.vc-graz.ac.at) joined #forth 08:20:35 --- join: GeDaMo (n=gedamo@212.225.115.246) joined #forth 08:34:26 --- quit: kar8nga (Remote closed the connection) 09:52:19 --- quit: maht (Read error: 54 (Connection reset by peer)) 09:53:37 --- join: maht (n=maht__@85-189-31-174.proweb.managedbroadband.co.uk) joined #forth 10:01:48 --- join: Tesla_ (n=info@58.248.188.164) joined #forth 10:14:34 --- quit: Tesla (Read error: 110 (Connection timed out)) 11:21:49 --- join: crc (n=crc@baconfile.com) joined #forth 11:23:30 --- quit: crc (Client Quit) 12:02:18 --- quit: Tesla_ (Remote closed the connection) 12:03:46 --- join: kar8nga (n=kar8nga@a-32.vc-graz.ac.at) joined #forth 12:04:15 --- join: Tesla (n=info@58.248.188.164) joined #forth 12:04:29 --- quit: tathi (Read error: 104 (Connection reset by peer)) 12:05:03 --- join: tathi (n=josh@dsl-216-227-91-166.fairpoint.net) joined #forth 13:40:34 --- quit: kar8nga (Remote closed the connection) 14:31:25 --- quit: GeDaMo ("Leaving.") 14:55:41 --- quit: Tesla (Read error: 113 (No route to host)) 14:56:54 --- join: Tesla (n=info@58.248.188.134) joined #forth 16:59:21 --- join: nighty__ (n=nighty@210.188.173.245) joined #forth 18:07:57 --- quit: nighty__ (Read error: 104 (Connection reset by peer)) 18:08:22 --- join: nighty__ (n=nighty@210.188.173.245) joined #forth 18:56:42 --- quit: proteusguy (Read error: 60 (Operation timed out)) 19:05:38 --- join: proteusguy (n=proteusg@61.7.144.97) joined #forth 19:11:00 --- join: xjrn (n=jim@astound-69-42-10-25.ca.astound.net) joined #forth 23:13:29 --- join: kar8nga (n=kar8nga@a-37.vc-graz.ac.at) joined #forth 23:56:34 --- quit: tathi (Read error: 110 (Connection timed out)) 23:57:36 --- quit: proteusguy (Read error: 60 (Operation timed out)) 23:59:59 --- log: ended forth/09.06.22