01:19:00 -!- calamari_ has quit ("<=K").
01:29:19 -!- lament has joined.
01:42:06 <lament> Taaus: http://www.unpronounceable.com/gould/
01:54:17 <lament> somebody started posting spam on the bfgolf forums
02:13:29 <lament> Taaus: listen to music samples.
02:14:22 <Taaus> I had no idea Gould's voice was so similar to Cartman's...
02:15:51 <Taaus> Ironically, you can hear some of Gould's actual humming on the "filtered" version.
02:17:43 <lament> well, it's clearly not perfect
02:17:47 <lament> but it does filter a lot!
02:18:27 <Taaus> Moving on to more esoteric matters... Are you familiar with the (La)TeX package called Xy-pic?
02:19:35 <Taaus> 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:29:46 <Taaus> It's a macro package for typesetting diagrams and graphs.
02:32:43 <Taaus> 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 <Taaus> Cool. I made it blow the stack with a loop.
02:38:14 <Taaus> @+(0,0) @@{@+(1,1)}
02:39:07 <Taaus> @+<coord> is "push <coord> onto stack", @@<coord> is "do <coord> for each item in stack"
02:40:49 <Taaus> Yes... Most of what this package does is to manipulate coordinates.
02:41:40 <lament> how do you do <coord> to a <coord>?
02:41:41 <Taaus> A stack operation counts as a <coord>. And { ... }is just to group more <coord>s as one <coord>.
02:42:42 <Taaus> Well, the <coord> popped from the stack is placed in a special variable called the "current coordinate".
02:43:26 <Taaus> The @+ operation doesn't affect the current coordinate, but it does push its argument onto the stack.
02:59:07 <Taaus> I guess you could implement a kind of truth values using empty/non-empty stacks...
02:59:23 <Taaus> It's possible to save stacks in variables, BTW.
03:24:37 <lament> is a stack just a type of coordinate? :)
03:25:02 <Taaus> Well, yes. All variables are :)
03:25:30 <Taaus> <coord>="<id>" saves <coord> for later use in "<id>"
03:29:06 <Taaus> Formally, every diagram is <pos> <decor>, where <pos> ::= <coord> |<pos><some operation><coord>
03:30:02 <Taaus> All of these set c (the current coordinate) to <pos>, and then do whatever the <operation> describes.
03:41:04 <Taaus> 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.