--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/paste/paste.24412	Wed Apr 24 01:43:10 2013 +0000
@@ -0,0 +1,301 @@
+2007-01-15.txt:17:15:34: -!- ais523 has joined #esoteric.
+2007-01-15.txt:17:16:16: <ais523> So there are people on #esoteric at the moment after all, then? I was monitoring the logs to see if anyone was online, but somehow I never seem to be online at the same time as other people...
+2007-01-15.txt:17:16:51: <ais523> !help
+2007-01-15.txt:17:17:02: <ais523> !help fyb
+2007-01-15.txt:17:17:40: <ais523> !fyb :>+!;
+2007-01-15.txt:17:18:19: <ais523> !ps
+2007-01-15.txt:17:18:22: <EgoBot> 1 ais523: ps
+2007-01-15.txt:17:19:00: <ais523> After that publicly-visible error message, EgoBot started spamming me with error messages...
+2007-01-15.txt:17:20:40: <ais523> Besides, how can it run a single fyb program anyway, considering that two of them, using each other as data space, are needed for the program to work?
+2007-01-15.txt:17:22:06: <ais523> !fyb file://bomber.fyb
+2007-01-15.txt:17:23:25: <ais523> I think it tries to run the program it's given against an internal list of programs to compete against, but it's getting 'permission denied' errors on the programs it has stored
+2007-01-15.txt:17:23:41: <ais523> !ps
+2007-01-15.txt:17:23:43: <EgoBot> 1 ais523: ps
+2007-01-15.txt:17:24:15: * ais523 discovers that giving EgoBot another command stops the error-message spam
+2007-01-15.txt:17:24:33: <ais523> !fybs :>+!;
+2007-01-15.txt:17:26:12: <ais523> !ps
+2007-01-15.txt:17:26:15: <EgoBot> 1 ais523: ps
+2007-01-15.txt:17:26:25: <ais523> It just sent me three hyphens and stopped...
+2007-01-15.txt:17:29:00: <ais523> !unlambda ```s``s``sii`ki`k.*``s``s`ks``s`k`s`ks``s`k`s`k./``s`k`sikk`k``s`ksk
+2007-01-15.txt:17:29:23: <ais523> I suppose so, it wasn't a very good program...
+2007-01-15.txt:17:30:12: <ais523> !fybs +[>[-]!+]
+2007-01-15.txt:17:30:46: <ais523> More hyphens. But that's a really vulnerable program, due to the tight loop near the start...
+2007-01-15.txt:17:36:29: <ais523> !fyb {>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>{>>>}{>>>}[-]++++++++++++++!}
+2007-01-15.txt:17:36:43: <ais523> !ps
+2007-01-15.txt:17:37:22: <EgoBot> 1 ais523: fyb
+2007-01-15.txt:17:37:24: <EgoBot> 2 ais523: ps
+2007-01-15.txt:17:37:52: <ais523> Hey, I think I actually beat some of its library
+2007-01-15.txt:17:38:11: <ais523> !fybs {>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>{>>>}{>>>}[-]++++++++++++++!}
+2007-01-15.txt:17:38:41: <ais523> More hyphens, but there was something encouraging in the error messages on the plain fyb
+2007-01-15.txt:17:42:34: <ais523> !fyb %:[%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%[-]!]>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>{>>>}{>>>}[-]++++++++++++++!;{{>>>>}{>>>>}[-]++++++++++++++!}
+2007-01-15.txt:17:42:45: <ais523> Hello, pikhq!
+2007-01-15.txt:17:45:05: <ais523> Yes, I'm enjoying esolangs. I enjoyed the logs, too, before I had access to an IRC client.
+2007-01-15.txt:17:45:26: <ais523> !ps
+2007-01-15.txt:17:45:29: <EgoBot> 1 ais523: ps
+2007-01-15.txt:17:45:57: <ais523> The new program seems less good than the old one. Maybe it's better to be simple...
+2007-01-15.txt:17:47:17: <ais523> !fyb :>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>{>>>}{>>>}[-]+++++++++++++++!;:>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>{>>>}{>>>}[-]+++++++++++++++!;>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>{>>>}{>>>}[-]+++++++++++++++!;
+2007-01-15.txt:17:48:03: <ais523> !ps
+2007-01-15.txt:17:48:07: <ais523> losing again...
+2007-01-15.txt:17:48:07: <EgoBot> 1 ais523: ps
+2007-01-15.txt:17:49:19: * ais523 tries something really simple
+2007-01-15.txt:17:49:43: <ais523> !fyb {>>>}{>>>}+++++++++++++++!
+2007-01-15.txt:17:50:25: <ais523> !help
+2007-01-15.txt:17:51:43: <ais523> !ps
+2007-01-15.txt:17:51:46: <EgoBot> 1 ais523: ps
+2007-01-15.txt:17:52:20: <ais523> The ps command does seems to stop the flow of error messages and useful answers... (it lost every single game, BTW)
+2007-01-15.txt:17:53:24: <ais523> Hey, how does EgoBot manage the 2D languages?
+2007-01-15.txt:17:54:06: <ais523> !help 1l
+2007-01-15.txt:17:54:27: <ais523> Oh, it seems that it reads it off the Web
+2007-01-15.txt:17:56:22: <ais523> !1l http://esoteric.voxelperfect.net/files/1l/src/1l_a/a.1l
+2007-01-15.txt:17:57:42: <ais523> !help
+2007-01-15.txt:17:58:11: <ais523> It doesn't have any of my languages either.
+2007-01-15.txt:17:59:07: <ais523> BackFlip, Underload, and MiniMAX are the main ones (there are also some BackFlip derivatives like ABCDXYZ and Unassignable)
+2007-01-15.txt:18:00:29: <ais523> How do you do a loop in Dimensifuck? The wiki isn't clear on how you affect the program flow
+2007-01-15.txt:18:02:06: <ais523> So v and ^ affect the program counter?
+2007-01-15.txt:18:03:53: <ais523> So you could compile BF into 2D Dimensifuck just by drawing loops to represent literal loops, in much the same way as Sansism
+2007-01-15.txt:18:05:14: <ais523> Maybe it would be possible to do it without wire-crossings
+2007-01-15.txt:18:11:41: <ais523> !fybs {>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>{>>>}{>>>}[-]++++++++++++++!}
+2007-01-15.txt:18:19:13: <ais523> If you assign each loop its own y-coordinate (or better, its own dimension), you could use each of those as a bypass path for the loop if the value is zero
+2007-01-15.txt:18:19:22: <ais523> and assign another one for the return path
+2007-01-15.txt:18:20:12: <ais523> + - < > , . are all the same in DF, so it's only the flow control you have to deal with
+2007-01-15.txt:18:22:23: -!- ais523 has quit ("about to lose Internet access for a while").
+2007-01-16.txt:09:13:38: -!- ais523 has joined #esoteric.
+2007-01-16.txt:09:14:10: <ais523> !fyb >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>{>>>}{>>>}[-]++++++++++++++!
+2007-01-16.txt:09:17:05: <ais523> !ps
+2007-01-16.txt:09:17:07: <EgoBot> 1 ais523: ps
+2007-01-16.txt:09:18:51: <ais523> !fyb :[>%%%%%%%%%%%%%%%%%%%%%%%%>[-]!<]*;:>>>>>>>>>>>>>>>>>>>>>>>>>>>{>>>}{>>>}[-]++++++++++++++!;{>>>}[-]++++++++++++++!
+2007-01-16.txt:09:19:42: <ais523> !ps
+2007-01-16.txt:09:19:46: <EgoBot> 1 ais523: fyb
+2007-01-16.txt:09:19:48: <EgoBot> 2 ais523: ps
+2007-01-16.txt:09:20:23: <ais523> it seems to be running all its example programs against each other, rather than against mine
+2007-01-16.txt:09:21:22: * ais523 tries a program designed only to lose
+2007-01-16.txt:09:21:38: <ais523> !fyb @[+]+++++++++++++!
+2007-01-16.txt:09:21:55: <ais523> !ps
+2007-01-16.txt:09:21:56: <EgoBot> 1 ais523: fyb
+2007-01-16.txt:09:21:58: <EgoBot> 2 ais523: ps
+2007-01-16.txt:09:22:10: <ais523> No, it's ignoring my program and just running its
+2007-01-16.txt:09:23:19: <ais523> !help
+2007-01-16.txt:09:23:32: <ais523> !ps
+2007-01-16.txt:09:23:34: <EgoBot> 1 ais523: ps
+2007-01-16.txt:09:23:55: <ais523> !fybs @[+]++++++++++++++!
+2007-01-16.txt:09:24:27: <ais523> !fybs >++!
+2007-01-16.txt:09:24:41: <ais523> !help
+2007-01-16.txt:09:24:52: <ais523> !help show
+2007-01-16.txt:09:25:01: <ais523> !help flush
+2007-01-16.txt:09:25:09: <ais523> !help usertrig
+2007-01-16.txt:09:25:24: <ais523> !help i
+2007-01-16.txt:09:25:38: <ais523> !help daemon
+2007-01-16.txt:09:26:30: <ais523> !unlambda ```sr.a``sr.b
+2007-01-16.txt:09:26:44: <ais523> That's an infinite loop, by the way
+2007-01-16.txt:09:26:47: <ais523> !ps
+2007-01-16.txt:09:26:48: <EgoBot> 1 ais523: unlambda
+2007-01-16.txt:09:26:50: <EgoBot> 2 ais523: ps
+2007-01-16.txt:09:26:58: <ais523> !kill 1
+2007-01-16.txt:09:27:25: <ais523> and only now do I get the output...
+2007-01-16.txt:09:28:30: <ais523> !flush
+2007-01-16.txt:09:28:41: <ais523> !ps
+2007-01-16.txt:09:29:20: <ais523> it's still busy sending me an infinite number of 'b's
+2007-01-16.txt:09:33:02: <ais523> !bf +[]
+2007-01-16.txt:09:33:13: <ais523> !ps
+2007-01-16.txt:09:33:46: <ais523> I can't even stop the infinite output loop with an infinite loop in another language...
+2007-01-16.txt:09:35:16: -!- ais523 is now known as ais523_trying_to.
+2007-01-16.txt:09:35:28: -!- ais523_trying_to is now known as ais523.
+2007-01-16.txt:09:35:58: -!- ais523 is now known as ais523_.
+2007-01-16.txt:09:36:19: <ais523_> Renaming myself to direct EgoBot's infinite output elsewhere
+2007-01-16.txt:09:37:04: <ais523_> !ps
+2007-01-16.txt:09:37:26: * ais523_ has probably broken EgoBot
+2007-01-16.txt:09:38:59: <ais523_> !ps
+2007-01-16.txt:09:39:13: <ais523_> It still seems to be in an infinite loop...
+2007-01-16.txt:09:47:56: <ais523_> !ps
+2007-01-16.txt:09:48:08: <ais523_> !help
+2007-01-16.txt:09:48:27: <ais523_> (I'm just trying this every now and then to see if it's finished it's infiniely-long output)
+2007-01-16.txt:09:51:07: <ais523_> !help
+2007-01-16.txt:09:56:53: <ais523_> !help
+2007-01-16.txt:10:00:01: <ais523_> !help
+2007-01-16.txt:10:00:16: -!- ais523_ is now known as ais523.
+2007-01-16.txt:10:00:26: -!- ais523 is now known as ais523_.
+2007-01-16.txt:10:00:33: <ais523_> it's still going...
+2007-01-16.txt:10:09:01: <ais523_> !help
+2007-01-16.txt:10:37:00: <ais523_> !help
+2007-01-16.txt:10:41:29: <ais523_> !help
+2007-01-16.txt:10:45:25: <ais523_> !help
+2007-01-16.txt:10:45:32: -!- ais523_ is now known as ais523.
+2007-01-16.txt:10:45:44: -!- ais523 is now known as ais523_.
+2007-01-16.txt:10:46:25: <ais523_> There should probably be some way to stop EgoBot in such situations (it was still sending messages when I checked just now)
+2007-01-16.txt:10:50:27: <ais523_> !help
+2007-01-16.txt:10:56:02: <ais523_> !help
+2007-01-16.txt:11:03:04: <ais523_> !help
+2007-01-16.txt:11:08:09: -!- ais523_ has quit ().
+2007-01-16.txt:12:00:30: -!- ais523 has joined #esoteric.
+2007-01-16.txt:12:00:50: -!- ais523 is now known as ais523_.
+2007-01-16.txt:12:11:58: <ais523_> !help
+2007-01-16.txt:12:33:25: <ais523_> that statement's rather out of context to me at the moment
+2007-01-16.txt:12:33:47: <ais523_> you should try to do it with setjmp
+2007-01-16.txt:12:33:57: <ais523_> both techniques have been used to implement Threaded INTERCAL
+2007-01-16.txt:12:36:03: <SimonRC> ais523_: actually setjmp is unlikely to work, and certainly not guaranteed.
+2007-01-16.txt:12:36:31: <ais523_> setjmp has certain guarantees. With practice and careful use of 'volatile', they can be exploited to lead to a portable program
+2007-01-16.txt:12:39:20: <ais523_> yes, you have to have all the coroutines in the same level of the same function
+2007-01-16.txt:12:39:33: <ais523_> but the same restriction applies to switch and to goto
+2007-01-16.txt:12:41:02: <ais523_> my Threaded INTERCAL code is at http://esoteric.voxelperfect.net/files/intercal (along with the rest of the INTERCAL implementation), in unravel.c
+2007-01-16.txt:12:41:27: <ais523_> I used setjmp to minimize the change needed to the existing code
+2007-01-16.txt:12:42:54: -!- ais523_ has quit ("lunchtime").
+2007-01-16.txt:13:01:53: -!- ais523_ has joined #esoteric.
+2007-01-16.txt:13:02:05: -!- ais523_ is now known as ais523.
+2007-01-16.txt:13:02:12: -!- ais523 is now known as ais523_.
+2007-01-16.txt:13:02:19: <ais523_> EgoBot's still going...
+2007-01-16.txt:13:08:45: -!- ais523_ is now known as ais523.
+2007-01-16.txt:13:09:27: <ais523> So EgoBot's left, and hasn't come back in.
+2007-01-16.txt:13:09:35: * ais523 is sorry for getting EgoBot thrown off the channel
+2007-01-16.txt:13:53:43: <ais523> Inertia?
+2007-01-16.txt:13:55:03: -!- ais523 has quit ("busy in RL").
+2007-01-17.txt:11:48:01: -!- ais523 has joined #esoteric.
+2007-01-17.txt:12:02:11: -!- ais523 changed the topic of #esoteric to: #esoteric - the international hub for esoteric programming language design and deployment - map: http://www.frappr.com/esolang - forum: http://esolangs.org/forum/ - EgoBot: !help (currently down) - wiki: http://esolangs.org/wiki/ - logs: http://tunes.org/~nef/logs/esoteric/ or http://meme.b9.com/cdates.html?channel=esoteric - for brainfuck-specific discussion, go to ##brainfuck - IRP ALLOWED - Pastebin: http://pastebin.ca/
+2007-01-17.txt:12:02:30: <ais523> For those who don't know, it was me who caused EgoBot to crash
+2007-01-17.txt:12:03:13: <ais523> I fed it an infinite loop written in Unlambda, and it sent me an infinite number of copies of the letter 'b' in response, until it got thrown out
+2007-01-17.txt:14:05:11: -!- ais523 has quit ("this quit message is boring").
+2007-01-30.txt:12:53:55: -!- ais523 has joined #esoteric.
+2007-01-30.txt:12:54:04: <ais523> !help
+2007-01-30.txt:12:55:49: * ais523 checks what happened to EgoBot
+2007-01-30.txt:12:56:21: <ais523> It seems it quit at 02:31:18 (110:Connection timed out) and didn't join again
+2007-01-30.txt:12:57:02: <ais523> That's a shame, I was wondering about a BF problem that's been bothering me
+2007-01-30.txt:12:57:51: <ais523> I'm not sure what it would look like. Maybe a Turing Machine?
+2007-01-30.txt:12:58:32: <ais523> Anyway, the problem was to write an 8-bit BF program which outputted another BF program that was an infinite loop
+2007-01-30.txt:12:58:50: <ais523> that's easy, but I was wondering how short you could get the first program
+2007-01-30.txt:12:59:08: <ais523> You could write something that just output +[], but there's probably a shorter way that produces more output
+2007-01-30.txt:13:04:18: <ais523> but making it longer might make it easier to generate
+2007-01-30.txt:13:04:31: * ais523 gets out an ASCII code table
+2007-01-30.txt:13:06:26: <ais523> -/13579;=?ACEGIKMOQSUWY[] is an infinite loop
+2007-01-30.txt:13:06:40: <ais523> and probably easier to generate
+2007-01-30.txt:13:10:09: <ais523> but assuming we don't want infinitely-long output, there has to be some way to stop it continuing along the same pattern
+2007-01-30.txt:13:13:10: <ais523> if we store 44 in a cell somehow, then the rest of the code can just be [+.+] (because -'s ASCII code is 45), and it will continue into the high reaches of ASCII before wrapping round to 0
+2007-01-30.txt:13:14:44: <ais523> but + has an ASCII code of 43, so if you do that you get +-[] with comments removed, which is a NOP
+2007-01-30.txt:13:15:09: * ais523 looks up 44 on the wiki's BF constant table
+2007-01-30.txt:13:15:25: <ais523> My first attempt is ++[>+<------]>+[+.+]
+2007-01-30.txt:13:15:35: <ais523> 20 characters
+2007-01-30.txt:13:26:53: <ais523> +[+.+.++++.+] works (13 characters)
+2007-01-30.txt:13:58:16: -!- ais523 has quit ().
+2007-01-31.txt:12:54:25: -!- ais523 has joined #esoteric.
+2007-01-31.txt:13:03:01: -!- ais523 is now known as ais523_.
+2007-01-31.txt:13:10:24: -!- ais523_ is now known as ais523.
+2007-01-31.txt:13:10:41: -!- ais523 has quit ().
+2007-01-31.txt:13:10:57: -!- ais523 has joined #esoteric.
+2007-01-31.txt:13:27:58: <ais523> MM2: 2, 3, 5, 8, 13. Sorry, this IRP implementation has a lag of a little over 10 hours at the moment.
+2007-01-31.txt:13:37:44: -!- ais523 has quit (Remote closed the connection).
+2007-01-31.txt:13:39:48: -!- ais523 has joined #esoteric.
+2007-01-31.txt:13:42:02: <ais523> Besides, this IRP implementation is wrong. I meant 2, 3, 5, 7, 11.
+2007-01-31.txt:13:49:33: <ais523> Hello, calamari
+2007-01-31.txt:13:49:43: <calamari> hi ais523
+2007-01-31.txt:13:50:12: <ais523> No, I just don't get to access IRC very often
+2007-01-31.txt:13:50:27: <ais523> and when I do, there rarely seems to be a discussion
+2007-01-31.txt:13:50:41: <ais523> so I just say hello to people when they join
+2007-01-31.txt:13:51:25: <ais523> !help
+2007-01-31.txt:13:51:35: <ais523> EgoBot's still down, isn't it?
+2007-01-31.txt:13:52:40: <ais523> I was discussing a brainfuck problem with SimonRC yesterday
+2007-01-31.txt:13:53:08: <ais523> the problem was to write the shortest possible 8-bit wrapping BF program that would output a BF program that was an infinite loop
+2007-01-31.txt:13:54:10: * ais523 checks the logs
+2007-01-31.txt:13:54:18: <ais523> it seems my best attempt was +[+.+.++++.+]
+2007-01-31.txt:14:12:39: <ais523> there are a lot of control characters in the output
+2007-01-31.txt:14:12:47: <ais523> but BF interpreters don't care about them
+2007-01-31.txt:14:16:38: <ais523> E!ps
+2007-01-31.txt:14:17:15: <ais523> E!1 e
+2007-01-31.txt:14:17:32: <ais523> E!1 e\n
+2007-01-31.txt:14:17:46: <ais523> E!1 a\n
+2007-01-31.txt:14:17:58: <ais523> E!1 i
+2007-01-31.txt:14:18:05: <ais523> E!1 i\n
+2007-01-31.txt:14:18:22: <ais523> E!1 o\n
+2007-01-31.txt:14:18:42: <ais523> E!1 f\n
+2007-01-31.txt:14:18:56: <ais523> E!1 r\n
+2007-01-31.txt:14:19:20: <ais523> E!1 t\n
+2007-01-31.txt:14:19:34: <ais523> E!1 m\n
+2007-01-31.txt:14:19:49: <ais523> E!1 k\n
+2007-01-31.txt:14:20:01: <ais523> E!1 w\n
+2007-01-31.txt:14:20:49: <ais523> E!help
+2007-01-31.txt:14:21:00: <ais523> E!ls
+2007-01-31.txt:14:21:14: <ais523> E!ps
+2007-01-31.txt:14:21:24: <ais523> E!kill 1
+2007-01-31.txt:14:23:23: <ais523> E!bf >,----------[>,----------]<[<]>[++++++++++.>]<[<]>[.>]
+2007-01-31.txt:14:23:27: <ais523> E!ps
+2007-01-31.txt:14:23:28: <EsoBot> 1:ais523
+2007-01-31.txt:14:23:43: <ais523> E!1 Hello, world!
+2007-01-31.txt:14:23:48: <ais523> E!1 \n
+2007-01-31.txt:14:24:01: <ais523> E!ps
+2007-01-31.txt:14:24:56: <ais523> E!bf +[>>,----------[>,----------]<[<]>[++++++++++.>]<[<]>[.>]<[[-]<]<]
+2007-01-31.txt:14:25:14: <ais523> E!1 Hello, world!\n
+2007-01-31.txt:14:25:21: <ais523> E!1 and again!\n
+2007-01-31.txt:14:25:42: <ais523> ~help
+2007-01-31.txt:14:26:04: <ais523> E!ps
+2007-01-31.txt:14:26:05: <EsoBot> 1:ais523
+2007-01-31.txt:14:26:31: <ais523> E!1 E!1\n \n
+2007-01-31.txt:14:26:54: <ais523> E!1 E!1 \\n \n
+2007-01-31.txt:14:27:24: <ais523> E!1 \n
+2007-01-31.txt:14:27:30: <ais523> e!ps
+2007-01-31.txt:14:27:31: <ais523> E!ps
+2007-01-31.txt:14:27:33: <EsoBot> 1:ais523
+2007-01-31.txt:14:37:49: <ais523> E!unnecessary
+2007-01-31.txt:14:38:01: <ais523> e!unnecessary Hello, world!
+2007-01-31.txt:14:38:06: <ais523> E!unnecessary Hello, world!
+2007-01-31.txt:14:39:31: <ais523> E!unnecessary CRITICAL ERROR: The file exists!
+2007-01-31.txt:14:40:05: <ais523> E!1 E!1 \\
+2007-01-31.txt:14:40:15: <ais523> E!1 n \n
+2007-01-31.txt:14:40:39: <ais523> E!1 E!1 E!1 \\
+2007-01-31.txt:14:40:43: <ais523> E!1 n \n
+2007-01-31.txt:14:42:47: <ais523> ~exec sys.stdout("testing");
+2007-01-31.txt:14:43:26: <ais523> E!1 ~sys.stdout("E!1 testing\\n"); \n
+2007-01-31.txt:14:43:53: <ais523> E!1 ~sys.stdout("E!1 testing\\
+2007-01-31.txt:14:43:59: <ais523> E!1 n"); \n
+2007-01-31.txt:14:44:31: <ais523> E!1 ~exec sys.stdout("testing\\
+2007-01-31.txt:14:44:37: <ais523> E!1 n"); \n
+2007-01-31.txt:14:45:35: <ais523> E!1 ~exec sys.stdout(";\n
+2007-01-31.txt:14:45:45: <ais523> E!1 ~exec sys.stdout(";)\n
+2007-01-31.txt:14:45:54: <ais523> E!1 ~exec sys.stdout(");\n
+2007-01-31.txt:14:46:11: <ais523> E!1 ~exec sys.stdout(");\n
+2007-01-31.txt:14:46:21: <ais523> E!ps
+2007-01-31.txt:14:47:16: <ais523> ~exec sys.stdout("E!ps");
+2007-01-31.txt:14:47:32: <ais523> E!quit
+2007-01-31.txt:14:49:49: <EsoBot> 1:ais523
+2007-01-31.txt:14:49:49: <EsoBot> 1:ais523
+2007-01-31.txt:14:49:49: -!- EsoBot has quit ("requested by ais523").
+2007-01-31.txt:15:37:39: <ais523> ~exec sys.stdout("test" * 2);
+2007-01-31.txt:16:52:33: <ais523> ...and you know you're too addicted to phpBB when you actually learn Visual Basic so that you can program Word to interpret it correctly
+2007-01-31.txt:17:00:55: <ais523> Can't you edit it in an external editor and then copy-and-paste it in?
+2007-01-31.txt:18:20:34: -!- ais523 has quit ().
+2007-02-02.txt:16:50:21: -!- ais523 has joined #esoteric.
+2007-02-02.txt:17:18:47: -!- ais523 has quit ().
+2007-02-05.txt:17:37:59: -!- ais523 has joined #esoteric.
+2007-02-05.txt:18:06:50: -!- ais523 has quit ().
+2007-02-20.txt:10:31:37: -!- ais523 has joined #esoteric.
+2007-02-20.txt:11:16:32: <ais523> I was impressed with Keymaker's Underload interpreter in Brainfuck
+2007-02-20.txt:11:16:56: <ais523> so I wrote a Brainfuck (minus input) to Underload compiler: http://pastebin.ca/364737
+2007-02-20.txt:11:21:18: <ais523> !help daemon
+2007-02-20.txt:11:21:48: <ais523> !daemon ul bf http://www.bf-hacks.org/hacks/uload.b
+2007-02-20.txt:11:22:01: <ais523> !ul (Hello, world!)S
+2007-02-20.txt:11:22:18: <ais523> !ps
+2007-02-20.txt:11:22:21: <EgoBot> 2 ais523: ps
+2007-02-20.txt:11:23:38: <ais523> !help bf
+2007-02-20.txt:11:24:26: <ais523> !daemon ul bf http://www.bf-hacks.org/hacks/uload.b
+2007-02-20.txt:11:24:30: <ais523> !ps
+2007-02-20.txt:11:24:34: <EgoBot> 3 ais523: ps
+2007-02-20.txt:11:24:55: <ais523> You can write the source code straight in, like this:
+2007-02-20.txt:11:25:04: <ais523> !bf +++++++++++++++++++++++++++++++++++.+.+.+.+.
+2007-02-20.txt:11:25:27: <ais523> but for some reason, daemoning the Underload compiler doesn't seem to take
+2007-02-20.txt:11:26:22: <ais523> !daemon ul bf8 http://www.bf-hacks.org/hacks/uload.b
+2007-02-20.txt:11:26:26: <ais523> !ps
+2007-02-20.txt:11:26:30: <EgoBot> 4 ais523: ps
+2007-02-20.txt:11:27:49: <ais523> !daemon dup bf >+[>,]<[<]>[>.]<[<]>[>.]
+2007-02-20.txt:11:27:53: <ais523> !ps
+2007-02-20.txt:11:27:56: <EgoBot> 5 ais523: ps
+2007-02-20.txt:11:28:04: <ais523> !dup Hello, world!
+2007-02-20.txt:11:28:26: <ais523> That's strange, there's no output but there isn't an error message either.
+2007-02-20.txt:11:28:35: <ais523> !this makes no sense and should cause an error message
+2007-02-20.txt:11:28:47: <ais523> !undaemon dup
+2007-02-20.txt:11:29:55: <ais523> !daemon dup bf >++++++++++++++++++++++++++++++++[>,----------]<[<]>[++++++++++.>]<[<]>[>.]
+2007-02-20.txt:11:30:05: <ais523> !dup Hello, world!
+2007-02-20.txt:11:30:42: <ais523> The problem seems to be that EgoBot is interpreting newline as newline (10), not EOF
+2007-02-20.txt:11:31:03: <ais523> !undaemon ul
+2007-02-20.txt:11:31:10: <ais523> !undaemon ul
+2007-02-20.txt:11:31:24: <ais523> !ps
+2007-02-20.txt:11:31:26: <EgoBot> 3 ais523: ps
+2007-02-20.txt:11:31:40: <ais523> There are still two broken daemons lying around, it seems
+2007-02-20.txt:11:31:49: <ais523> !undaemon ul
+2007-02-20.txt:11:31:58: <ais523> !help eof
+[too many lines; stopping]