00:40:50 <ihope> I need an emoticon with a guy that's raising his eyebrows, and sorta leaning back a bit.
00:41:03 <ihope> All in text format, with a maximum of 3 characters...
00:48:48 <GregorR> G'luck.
00:49:04 <GregorR> \:-|
01:54:02 -!- Arrogant has joined.
01:54:16 <pgimeno> |-B
01:54:38 <Arrogant> \-:
01:54:47 <pgimeno> (-B
01:55:21 -!- Arrogant has changed nick to Arrogant[RE4].
01:56:11 <GregorR> |:|
02:06:59 <ihope> Now, the phrase "muchas muchachas" sounds very :-).
02:17:44 -!- GregorR has quit (Read error: 104 (Connection reset by peer)).
02:18:04 -!- GregorR has joined.
02:38:55 -!- Arrogant[RE4] has changed nick to Arrogant.
02:50:56 -!- ihope has quit (Read error: 110 (Connection timed out)).
03:15:51 * SimonRC goes top bed
03:22:27 <GregorR> I CALL BOTTOM BUNK 8-D
03:24:01 <SimonRC> *to bed
04:32:45 -!- kipple has quit (Read error: 110 (Connection timed out)).
05:24:45 -!- Arrogant has quit ("Leaving").
06:12:12 -!- GregorR has quit (Read error: 104 (Connection reset by peer)).
06:12:21 -!- GregorR has joined.
07:59:59 -!- clog has quit (ended).
08:00:00 -!- clog has joined.
10:15:59 -!- CXI has joined.
10:34:05 -!- int-e has joined.
14:35:06 -!- ihope has joined.
14:40:58 <ihope> So . is infixr 9, right?
14:57:02 <int-e> you can use  :info (.)  in ghci to find that out (yes it is).
14:58:02 -!- lynxtor has joined.
14:58:06 <lynxtor> hi :)
14:58:36 -!- sp3tt has quit (Nick collision from services.).
15:05:35 <ihope> int-e: :info . will work too
15:05:48 <ihope> This doesn't work, though:
15:05:50 <ihope> @type .
15:06:09 <lynxtor> is this a language, or console commands
15:06:09 <ihope> Hmm, thought I was in #haskell.
15:06:32 <ihope> Haskell is a programming language...
15:07:15 <lynxtor> cool. is it esoteric?
15:08:36 <ihope> Nope.
15:08:43 <lynxtor> ah, ok
15:09:09 <ihope> It is, however, one of the most "different" programming languages I know.
15:10:33 <lynxtor> anyway, i was thinking about writing a brainfuck to C "compiler"
15:10:36 <lynxtor> errrrrrrrr
15:10:41 <lynxtor> *C to BF
15:10:52 <lynxtor> BF to C would be incredibly simple :)
15:11:17 <ihope> Heh.
15:11:48 <lynxtor> I know it's possible... it started off with me thinking about how functions would operate in BF
15:15:11 <ihope> Say... has anybody ever needed a 3-walk thingy?
15:19:45 <lynxtor> What's that
15:24:22 <lynxtor> (Excuse my n00bishness... I'm 18, and I only recently got into the esolang scene)
15:24:50 <ihope> Well, I pretty much just made up the term :-P
15:25:08 <lynxtor> Heh, then how would people know what it was?
15:25:47 <ihope> That's when a BF program uses every third space for "normal" memory, reserving another third of them for subroutines and the last third for sub-subroutines.
15:26:32 <lynxtor> Right.
15:27:04 <lynxtor> Well... I haven't programmed enough in BF to use subroutines, but I envisioned that it would happen anyway
15:27:11 * ihope writes "How to Emulate BF in BF"
15:27:50 <ihope> Well, I oughta revert this vandalism.
15:28:04 <lynxtor> where? i want to see it before it gets deleted
15:28:33 <ihope> You'll be able to see it in the history, even if it gets reverted.
15:28:42 <SimonRC> how far has GregorR got with c2bf
15:28:43 <SimonRC> ?
15:29:13 <SimonRC> you may get more relevent bf stufff on ##brainfuck
15:29:13 <ihope> The pages are Y, Var, Var'aq, HQ9 Plus, BF instruction minimalization and Dumbf*ck.
15:29:29 <ihope> I still can't edit the wiki.
15:30:23 <ihope> There are THIRTEEN unreverted vandalisms.
15:30:40 <lynxtor> O_O
15:32:31 <lynxtor> if someone were to make a BF cpu, how would it handle the loops? it couldn't use jmps and a program counter like a "normal" CPU, it would have to read in the entire program and store the loop endings somewhere?
15:33:08 <ihope> Um...
15:33:18 <ihope> Why not just use the jumps and stuff?
15:34:00 <lynxtor> because normally jumps affect the program counter register, but there's no such thing in BF
15:34:20 <lynxtor> and using jumps would be un-BFlike :P
15:35:07 <ihope> Well, BF uses while loops.
15:35:36 <lynxtor> yeah
15:35:44 <lynxtor> the best kind of loop IMO :)
15:36:06 <ihope> BF-SC uses untils...
15:38:24 <lynxtor> BF-SC?
15:39:02 -!- sp3tt_ has joined.
15:39:02 <ihope> http://esoteric.voxelperfect.net/wiki/BF-SC
15:41:05 -!- sp3tt_ has changed nick to sp3tt.
15:52:26 <lynxtor> so GregorR's working on CtoBF? I thought calamari was doing that
15:57:49 -!- jix has joined.
16:12:34 <SimonRC> lynxtor: I could be wrong
16:12:42 <lynxtor> oh right
16:13:24 <jix> moin
16:13:42 <SimonRC> j0
16:14:39 <SimonRC> Anyway, you can handle BF loops with a simple stack
16:15:23 <lynxtor> ah of course
16:15:42 <ihope> How?
16:15:47 <lynxtor> i was thinking of designing a BF cpu... but before I do that, I want to make an emulator for it
17:52:30 -!- kipple has joined.
18:35:42 -!- ihope__ has joined.
18:36:06 -!- puzzlet_ has joined.
18:36:17 -!- puzzlet has quit (Read error: 104 (Connection reset by peer)).
18:36:24 <ihope__> Whee, underscore.
18:36:51 -!- ihope has quit (Nick collision from services.).
18:36:53 -!- ihope__ has changed nick to ihope.
18:38:59 <ihope> !RmE♥Es
18:39:01 <EgoBot> Huh?
18:39:45 <lynxtor> :O
18:41:49 <int-e> <CTCP>
19:11:38 -!- lynxtor has quit.
19:56:07 <ihope> int-e: how'd you do that?
19:56:38 <int-e> cut&paste ;)
19:56:48 <ihope> :-)
19:56:56 <ihope> • <- beep?
19:57:06 <ihope> Or bullet, or what?
19:57:47 * int-e wonders which unicode character that was
19:58:11 <ihope> So it wasn't an ASCII BEL?
19:58:13 <int-e> Bullet.
19:58:19 <int-e> U+2022
19:59:01 <int-e> 
19:59:04 <ihope> !bf +++++++. <- ASCII BEL
19:59:06 <EgoBot> 
19:59:15 <ihope> Okay, enough beeping.
20:00:43 <lament> beebeebeebeebeep
20:07:15 <ihope> Now let's see here...
20:07:41 -!- lindi- has left (?).
20:07:48 <ihope> *munch %%
20:13:47 -!- jix has quit ("Bitte waehlen Sie eine Beerdigungnachricht").
20:26:07 -!- ihope has quit (Remote closed the connection).
20:27:45 -!- ihope has joined.
20:28:44 <ihope> Ahh. I love PuTTYtel.
20:29:18 <ihope> I can't say it's easier to use than ChatZilla, but it's quite nice.
20:30:27 <int-e> hum. doesn't answering all those Pongs get annoying?
20:30:31 <int-e> err pings
20:30:53 <ihope> I don't get them very often.
20:32:14 <ihope> Maybe once I finish EagleBot (like that's ever going to happen), I'll use that as a chat client.
20:35:42 <ihope> There! A ping!
20:35:53 * ihope pongs
20:44:41 <ihope> http://dontclick.it/
20:51:03 <ihope> So it looks like the proper syntax thingy is PONG ihope :brown.freenode.net
21:09:36 <ihope> I expect to lag out once the next PONG doesn't happen... :-)
21:09:56 <ihope> Well, I suppose I ought to work on EagleBot.
21:10:09 <ihope> Then I can... well, you know the drill.
21:10:15 -!- ihope has quit ("EagleBot").
21:24:00 -!- int-e has quit ("Bye!").
23:23:37 -!- CXI has quit (Connection timed out).
23:29:00 -!- CXI has joined.