01:19:00 -!- calamari_ has quit ("<=K"). 01:29:19 -!- lament has joined. 01:42:06 Taaus: http://www.unpronounceable.com/gould/ 01:54:05 oh great 01:54:17 somebody started posting spam on the bfgolf forums 02:13:05 Mmmm... Gould. 02:13:29 Taaus: listen to music samples. 02:13:33 I did. 02:13:54 oh. Then don't. 02:14:22 I had no idea Gould's voice was so similar to Cartman's... 02:15:51 Ironically, you can hear some of Gould's actual humming on the "filtered" version. 02:17:43 well, it's clearly not perfect 02:17:47 but it does filter a lot! 02:17:57 True. 02:18:27 Moving on to more esoteric matters... Are you familiar with the (La)TeX package called Xy-pic? 02:18:47 no. 02:19:35 Okay. I'm not quite sure whether or not it should be considered esoteric. It's pretty widely used... The syntax is right up there, though. 02:28:08 what does it do? 02:29:46 It's a macro package for typesetting diagrams and graphs. 02:31:23 turing-complete? 02:32:43 I'm not sure.. It doesn't have any looping constructs, as far as I can see... Although it might be possible to implement it with a stack.. Hmm. 02:37:34 Cool. I made it blow the stack with a loop. 02:38:14 @+(0,0) @@{@+(1,1)} 02:39:07 @+ is "push onto stack", @@ is "do for each item in stack" 02:40:10 do ? 02:40:49 Yes... Most of what this package does is to manipulate coordinates. 02:41:40 how do you do to a ? 02:41:41 A stack operation counts as a . And { ... } is just to group more s as one . 02:42:42 Well, the popped from the stack is placed in a special variable called the "current coordinate". 02:43:26 The @+ operation doesn't affect the current coordinate, but it does push its argument onto the stack. 02:59:07 I guess you could implement a kind of truth values using empty/non-empty stacks... 02:59:23 It's possible to save stacks in variables, BTW. 03:24:37 is a stack just a type of coordinate? :) 03:25:02 Well, yes. All variables are :) 03:25:30 ="" saves for later use in "" 03:29:06 Formally, every diagram is , where ::= 03:30:02 All of these set c (the current coordinate) to , and then do whatever the describes. 03:41:04 Grr... Saving stacks in variables seems to be... Limited, somehow... It seems it has to take place directly after the stack has been initialised. 07:59:59 -!- clog has quit (ended). 08:00:00 -!- clog has joined. 08:59:56 -!- lament has quit ("leaving"). 23:59:24 -!- lament has joined.