00:20 (quit) dnolen: Quit: dnolen
00:44 (join) dnolen
00:44 (quit) dnolen: Client Quit
02:19 (quit) masm: Ping timeout: 276 seconds
03:04 (quit) martinhex: Remote host closed the connection
03:10 (join) martinhex
03:41 (quit) parcs: Ping timeout: 240 seconds
03:43 (join) parcs
04:34 (quit) jonrafkind: Ping timeout: 240 seconds
04:45 (join) sanxiyn
04:53 (join) Nanakhiel
04:56 (quit) Lajla: Ping timeout: 265 seconds
05:38 (join) mceier
05:49 (join) stis
05:49 (quit) sanxiyn: Quit: 전 이만 갑니다.
07:19 (join) masm
07:36 (join) sunnyps
08:06 (join) mheld
08:21 (nick) Nanakhiel -> Lajla
08:35 (quit) masm: Ping timeout: 240 seconds
08:49 (join) masm
08:58 (quit) Lajla: Ping timeout: 240 seconds
09:11 (quit) mceier: Quit: leaving
09:28 (join) Lajla
09:31 (join) MayDaniel
09:54 (quit) sunnyps: Quit: Leaving
10:04 (join) traisen
10:06 traisen: Simple textual Racket question: What option (-t  ?) and what Racket code is needed to run (+ 5 3) from file?
10:08 (join) corruptmemory
10:13 (join) aLeSD
10:29 (quit) mheld: Quit: mheld
10:30 traisen: never mind
10:31 (quit) traisen: Quit: Page closed
11:06 (join) mheld
11:09 (join) traisen
11:32 (join) anRch
11:51 (quit) aLeSD: Ping timeout: 255 seconds
11:51 (join) aLeSD
11:57 (quit) MayDaniel: Read error: Connection reset by peer
12:03 (quit) anRch: Quit: anRch
12:05 (join) mceier
12:12 (quit) mheld: Ping timeout: 250 seconds
12:12 (join) anRch
12:13 (quit) aLeSD: Ping timeout: 276 seconds
12:17 (quit) traisen: Quit: Page closed
12:20 (quit) anRch: Ping timeout: 240 seconds
12:25 (join) mheld
12:27 (join) anRch
12:40 (quit) anRch: Quit: anRch
12:55 (join) anRch
13:04 (quit) mheld: Ping timeout: 265 seconds
13:07 (quit) corruptmemory: Quit: Leaving
13:08 (join) corruptmemory
13:19 Lajla: corruptmemory,
13:19 Lajla: in sci-fi, you often encounter that.
13:20 Lajla: Like, a semi deus ex machina or what no that reveals that a lot of what has been happening was te result of some neural parasitic microbes which altered your memory.
13:20 corruptmemory: yes.  tis true. Alas, I tent to encounter it daily ;-)
13:21 corruptmemory: Or when I hack c/c++
13:22 Lajla: Your language emplying the existence C/C++ programs which are not hacked together?
13:22 Lajla: But it always happened in Voyager.
13:23 Lajla: Don't know, but in Voyager, too often a problem was solved by decabilibrating the dilithium injection array to funnel the warp plasm through the deflector disk to create a localized tachyon inversion.
13:23 Lajla: I did like the temporal paradox episodes, where the mystery turned out with that they started the whole problem with investigating it in the first place, but they used the idea a bit too often.
13:34 Lajla: Does anyone here have some example code of exceptions implemented with call/cc?
13:36 (join) jonrafkind
13:44 (join) MayDaniel
13:45 (join) mheld
13:51 (quit) MayDaniel: Read error: Connection reset by peer
14:14 (quit) corruptmemory: Remote host closed the connection
14:18 (join) corruptmemory
14:18 (quit) anRch: Quit: anRch
14:26 cky: Lajla: I can think of temporal paradoxes created with call/cc. :-P
14:29 Lajla: Dat is true.
14:29 Lajla: But call/cc is till cool.
14:29 Lajla: Like the dilithium injection array
14:33 (join) MayDaniel
15:28 (join) dnolen
15:55 (quit) MayDaniel: Read error: Connection reset by peer
15:57 (quit) dnolen: Quit: dnolen
16:06 clklein: Why does this program not print anything?
16:06 clklein: (parameterize ([current-error-port (open-output-nowhere)]) (error "bad"))
16:08 clklein: Isn't there some uncaught-exceptions handlers outside the dynamic extent of the parameterize that would print the exception?
16:11 jonrafkind: you mean that error should escape the extent of the parameterize and use the uncaught exception handler's error port?
16:11 clklein: right
16:11 jonrafkind: well sounds reasonable to me
16:12 jonrafkind: maybe the uncaught exception handler secretly uses the current parameterzations
16:12 jonrafkind: lets se..
16:12 clklein: I bet that's it.
16:12 jonrafkind: rudybot: (with-handlers ([exn? (lambda (e) 5)]) (parameterize ([current-error-port (open-output-nowhere)]) (error "bad")))
16:12 rudybot: jonrafkind: ; Value: 5
16:13 jonrafkind: rudybot: (with-handlers ([exn? (lambda (e) (current-error-port))]) (parameterize ([current-error-port (open-output-nowhere)]) (error "bad")))
16:13 rudybot: jonrafkind: ; Value: #<output-port:string>
16:15 clklein: I guess handlers don't run in the context I thought they did.
16:18 clklein: Time for some reading :)
16:22 (quit) martinhex: Read error: Connection reset by peer
16:23 (join) martinhex
17:02 (quit) tv|z: Ping timeout: 246 seconds
17:04 (join) tv|z
17:38 (join) MayDaniel
17:40 (quit) stis: Remote host closed the connection
17:55 Lajla: paramatrize is basically fluid-let?
17:55 Lajla: Or is there something more to it?
17:57 (quit) mheld: Ping timeout: 264 seconds
18:03 jonrafkind: yea I think so
18:15 (quit) jonrafkind: Ping timeout: 240 seconds
18:17 (join) mwolfe
18:33 (quit) mceier: Quit: Lost terminal
18:51 (join) mceier
18:51 (quit) mceier: Client Quit
18:57 (join) mceier
18:57 (join) dnolen
19:48 (join) mheld
19:53 (quit) masm: Quit: Leaving.
20:01 (quit) mceier: Quit: leaving
20:12 (quit) parcs: Ping timeout: 240 seconds
20:14 (join) parcs
20:30 (quit) MayDaniel: Read error: Connection reset by peer
21:42 (join) jonrafkind
22:21 (quit) dnolen: Quit: dnolen
23:18 (quit) corruptmemory: Ping timeout: 240 seconds
23:19 (join) Fare
23:23 (join) masm
23:27 (quit) masm: Client Quit