2005-07-26.txt:04:17:10: <int-e> I know. But I get user    0m2.131s for (my) bf2c then gcc and user    0m19.108s for bff :)
2005-07-26.txt:06:45:01: <int-e> :)
2005-07-26.txt:07:06:30: <int-e> ok, BF2C is boring :)
2005-07-26.txt:07:14:34: <int-e> yep, but not too bad either :)
2005-07-26.txt:07:25:41: <int-e> good luck :)
2005-07-26.txt:16:32:26: <int-e> BAAAAAAAAAAABAAAAAB prints a single A :)
2005-07-26.txt:18:15:06: <int-e> done :)
2005-07-26.txt:19:18:34: <int-e> XYYYYYYYYYYYYYXYYYYYX works too :)
2005-07-26.txt:20:12:02: <int-e> I was going to say: Gimme a spec. :)
2005-07-27.txt:12:31:12: <int-e> :)
2005-07-27.txt:12:39:56: <int-e> I could stop any moment :)
2005-07-27.txt:15:54:27: <int-e> do you know programming languages where (: and :) are language tokens?
2005-07-27.txt:21:09:46: <int-e> oh found another sun with gcc 3.4.2 :)
2005-07-27.txt:21:15:25: <int-e> I know :)
2005-07-27.txt:21:17:42: <int-e> :)
2005-07-27.txt:23:18:43: <int-e> AAAAAAAAAAARGH :)
2005-07-28.txt:00:40:26: <int-e> enough for all practical purposes, as I said :)
2005-07-28.txt:00:42:31: <int-e> graue, but 2^256 is close to that :)
2005-07-28.txt:00:50:37: <int-e> 0 is represented as 0 :)
2005-07-28.txt:01:10:14: <int-e> a machine should not run esolangs for any serious work :)
2005-07-29.txt:00:04:15: <int-e> well at least it works :)
2005-07-29.txt:00:50:13: <int-e> is valid :)
2005-08-01.txt:18:52:45: <int-e> aaaaaaaaaah :)
2005-08-01.txt:23:56:13: <int-e> it looks ugly :)
2005-08-05.txt:22:53:41: <int-e> hey, apparently that predecessor thingy was created by me, I even got credit :)
2005-08-06.txt:00:01:11: <int-e> :)
2005-08-06.txt:00:02:21: <int-e> that happens to me, too - but when I'm using a de layout keyboard :)
2005-08-10.txt:23:17:56: <int-e> :)
2005-08-10.txt:23:35:30: <int-e> It's only visible in strong magical fields. (Read some Terry Pratchett :)
2005-08-10.txt:23:36:23: <int-e> jix, it's pronounced 'red', but it's spelled 'read' :)
2005-08-10.txt:23:36:55: <int-e> :)
2005-08-11.txt:00:52:08: <int-e> :)
2005-08-16.txt:00:20:06: <int-e> :)
2005-08-16.txt:00:20:43: <int-e> :)
2005-08-17.txt:23:01:55: <int-e> and bsf :)
2005-08-24.txt:03:46:56: <int-e> it's voila :)
2005-08-31.txt:07:55:36: <int-e> :)
2005-12-03.txt:11:28:02: <int-e> well, do that two more times :)
2005-12-04.txt:11:43:17: <int-e> Keymaker: I chiseled off another 14 bytes from my entry last night :)
2005-12-04.txt:11:58:07: <int-e> that's a magical number :)
2005-12-04.txt:12:56:26: <int-e> and I wonder why I'm getting Cell value too small (-1) errors :)
2005-12-07.txt:13:48:07: <int-e> you might like this :)
2005-12-07.txt:14:03:10: <int-e> python quine :)
2006-01-12.txt:22:11:02: <int-e> | is really cool - in programs that don't do I/O :)
2006-01-12.txt:22:25:30: <int-e> then I'd claim that my C one is faster :)
2006-01-12.txt:22:32:23: <int-e> even for insanely call/cc-ing programs like quine12.unl :) (that's the one where mandelson-unlambda does so poorly)
2006-01-12.txt:22:44:44: <int-e> I should have thought of that :)
2006-01-12.txt:22:48:25: <int-e> ah, neat. then ``c`cc`c`r`.o`.o`.f`cc prints 'foo' over and over :)
2006-01-12.txt:22:54:17: <int-e> it can eat a lot of memory and run into infinite loops :)
2006-01-12.txt:23:33:15: <int-e> :)
2006-01-12.txt:23:36:02: <int-e> I think I got it. Luckily I kept the corresponding lambda terms around :)
2006-01-13.txt:00:08:44: <int-e> [[<]?] or [?[<]] :)
2006-01-13.txt:00:41:50: <int-e> ihope: nnn:@[>>[>]@[<]<]>[>.] ... this or something similar like that should print nnn digits :)
2006-01-29.txt:02:24:05: <int-e> the result is .c :)
2006-02-24.txt:02:16:44: <int-e> if your program contains ][, you're doing something wrong :)
2006-02-24.txt:20:14:34: <int-e> d'oh :)
2006-02-24.txt:20:21:51: <int-e> well, of course not :)
2006-02-24.txt:20:31:05: <int-e> right, you broke them :)
2006-02-24.txt:20:51:34: <int-e> I just didn't think of it :)
2006-02-25.txt:01:33:22: <int-e> you're mistaken. :)
2006-02-25.txt:01:55:12: <int-e> the first column are powers of two though :)
2006-02-25.txt:14:17:46: <int-e> dangit. :)
2006-02-25.txt:14:25:56: <int-e> but ... +[,[>++++<-],>[<++++++++>-]<.[-]+] is shorter :)
2006-02-25.txt:14:44:58: <int-e> I can do that :)
2006-02-25.txt:14:53:57: <int-e> :)
2006-03-05.txt:17:49:47: <int-e> sorry, just testing :)
2006-03-05.txt:17:54:07: <int-e> etaoinshrdlu :)
2006-03-05.txt:17:59:13: <int-e> maybe digits should not be allowed :)
2006-03-22.txt:21:13:21: <int-e> :)
2006-03-22.txt:21:18:44: <int-e> you get the idea :)
2006-03-22.txt:21:43:38: <int-e> the really funny thing is that this program worked the first time that I tried it :)
2006-03-22.txt:22:04:40: <int-e> :)
2006-10-05.txt:23:02:20: <int-e> (the txtgen code :)
2013-11-10.txt:01:03:21: <int-e> I forgot how icky that programming language (Unlambda) really is :)
2013-11-10.txt:11:33:02: <int-e> then it's not x86 :)
2013-11-10.txt:11:33:49: <int-e> x86 is certainly big enough for a UTM, given the right peripheral(s) :)
2013-11-10.txt:21:20:17: <int-e> I'm running it. Elliot more or less talked me into taking over. :)
2013-11-10.txt:21:21:47: <int-e> That's probably because I'm blissfully unaware of that channel :)
2013-11-11.txt:14:15:31: <int-e> ais523_: I did, but I didn't really think about it :)
2013-11-11.txt:14:16:07: <int-e> boily: I've been here before, but this time lambdabot dragged me here :)
2013-11-11.txt:14:17:23: <int-e> my most notable intercal accomplishment is a rot13 filter (50 lines without using standard library.) ... and without comments :)
2013-11-11.txt:19:54:50: <int-e> wisdom probability density function ... nice concept :)
2013-11-11.txt:21:09:11: <int-e> nooodl: I believe I've even used 'tac' once or twice ... :)
2013-11-11.txt:21:12:28: <int-e> the GNU 'tac' has a tac_seekable function, which hopefully does something clever :)
2013-11-11.txt:21:35:25: <int-e> Vorpal: but that's a small excuse for not noting that 512*24 is quite far from 22880 :)
2013-11-11.txt:22:13:41: <int-e> mouse in the middle :)
2013-11-11.txt:22:46:36: <int-e> fizzie: it didn't :)
2013-11-11.txt:22:52:50: <int-e> apparently, mentioning C++ no longer reduces one's karma (it did that for a while when karma was new) :)
2013-11-11.txt:22:55:16: <int-e> nooodl_: no, C++ was special-cased :)
2013-11-11.txt:23:09:08: <int-e> fun, I expected more than 4 draws (and fewer wins) :)
2013-11-11.txt:23:16:56: <int-e> ok, I'll stop there :)
2013-11-11.txt:23:18:23: <int-e> +. is a real suicide :)
2013-11-11.txt:23:26:55: <oerjan> <int-e> In any case, the most impressive Intercal program I know about is Ørjan's unlambda interpretet ( http://home.nvg.org/~oerjan/esoteric/intercal/ ) <-- :))
2013-11-12.txt:18:19:14: <int-e> Just don't uninstall libacl when coreutils are using it :) (that's about the worst I did, back when I was using Gentoo. I still compile the occasional kernel though, and a ton of Haskell stuff.)
2013-11-12.txt:18:20:16: <int-e> arch has binary packages :)
2013-11-12.txt:20:40:52: <int-e> and in any case, *I* killed it :)
2013-11-13.txt:15:48:07: <int-e> but it should still die with the virtual machine :)
2013-11-13.txt:15:57:08: <int-e> I forgot how hard to kill that : | : thing is ... now one reboot later :)
2013-11-13.txt:19:51:41: <int-e> ah so that's what this does :)
2013-11-13.txt:20:01:43: <int-e> better than apathy :)
2013-11-13.txt:20:11:04: <int-e> ais523: probably, if I wanted to do something not-so-stupid :)
2013-11-16.txt:22:58:39: <int-e> maybe I should pick a different name for my test bot :)
2013-11-17.txt:01:42:31: <int-e> @let fibs = fix ((0:) . scanl (+) 1)
2013-11-17.txt:12:04:18: <int-e> oh :)
2013-11-17.txt:17:55:03: <int-e> takes a cycle :)
2013-11-18.txt:13:09:09: <int-e> ok, I guess it's just too weird to really believe :)
2013-11-19.txt:16:47:19: <int-e> even flags are defined :)
2013-11-19.txt:16:48:26: <int-e> In any case, those processor manuals are the right place to look up such information :)
2013-11-19.txt:16:49:29: <int-e> (rflags is essentially set to 0, but there's a reserved bit that is forced to be 1 :) )
2013-11-19.txt:16:58:21: <int-e> so 65280. darn :)
2013-11-19.txt:16:59:55: <int-e> that said, I'm not sure whether .stack is allowed in the .tiny model :) It's been a while ...
2013-11-19.txt:17:11:35: <int-e> fs: is used for thread-local storage :)
2013-11-20.txt:21:53:32: <int-e> It's so unfair :)
2013-11-20.txt:22:03:51: <int-e> funny. google for "�" says it matches no pages. duckduckgo displays a picture of an elephant. duckduckgo won that round :)
2013-11-20.txt:22:06:11: <int-e> not sure whether that's lawful, but it doesn't get any more neutral :)
2013-11-21.txt:22:55:45: <int-e> oerjan: nothing. I'm adding default (Integer,Double) so your @let will hopefully stop working :)
2013-11-21.txt:22:57:56: <int-e> oerjan: yes, I added () there, too. thanks for the hint :)
2013-11-21.txt:23:26:51: <int-e> it's a bit annoying to have to restart lambdabot just because of an extra flag. oh well :)
2013-11-21.txt:23:29:57: <int-e> oerjan: thanks :)
2013-11-22.txt:19:23:02: <int-e> (maybe they didn't appreciate money back then? :) )
2013-11-22.txt:20:55:41: <int-e> (convert 0 <= al <= 15 to 0123456789ABCDEF ASCII:) cmp al, 10; sbb al, 69h; das
2013-11-22.txt:21:59:11: <int-e> b_jonas: see also the part after the ellipsis :)
2013-11-22.txt:22:02:42: <int-e> it's a terminal, which emulates a printer :)
2013-11-22.txt:22:29:45: <int-e> Even for x86, I should've written "near call" there :)
2013-11-22.txt:22:59:08: <int-e> confused that with inc/dec :)
2013-11-22.txt:23:01:16: <int-e> But there's no place for a 'test' in there :)
2013-11-22.txt:23:22:30: <int-e> Slereah: 256 bytes of addressable code wouldn't be enough or most purposes :)
2013-11-22.txt:23:35:18: <int-e> writing bad assembly code has been automated :)
2013-11-22.txt:23:48:51: <int-e> ais523: I expected 0.0 :)
2013-11-23.txt:00:02:17: <int-e> ais523: I bet -Os is not the primary focus of the gcc developers :)
2013-11-23.txt:00:11:23: <int-e> ais523: anyway, I'm not opposed to writing assembly code, but there should be a good reason :)
2013-11-23.txt:00:11:45: <int-e> fizzie: well, they don't :)