00:11:46 <cpressey> nooga: the interpreting loop of befunge is iterative, like: while(!done) { execute_at(x,y); x+=dx; y+=dy; }
00:17:52 <nooga> and dx and dy are depending on what interpreter have under ip?
00:18:39 <cpressey> yeah. >, for example, sets dx=1 and dy=0
00:23:07 <nooga> btw. excuse my english
01:02:32 -!- puzzlet_ has joined.
01:02:49 -!- puzlet has quit (Read error: 110 (Connection timed out)).
01:03:37 -!- nooga has quit (Read error: 113 (No route to host)).
01:50:33 -!- puzzlet_ has changed nick to puzzlet.
03:22:25 -!- puzlet has joined.
03:41:00 -!- puzzlet has quit (Read error: 110 (Connection timed out)).
03:57:26 -!- kpreid has quit.
04:42:55 -!- puzlet has changed nick to puzzlet.
05:26:20 -!- puzlet has joined.
05:35:06 -!- ChanServ has quit (ACK! SIGSEGV!).
05:36:52 -!- puzzlet has quit (Read error: 110 (Connection timed out)).
05:51:44 -!- ChanServ has joined.
05:51:44 -!- irc.freenode.net has set channel mode: +o ChanServ.
06:01:53 -!- puzzlet_ has joined.
06:03:18 -!- kpreid has joined.
06:12:15 -!- puzlet has quit (Read error: 110 (Connection timed out)).
06:12:34 -!- puzzlet has joined.
06:14:01 -!- puzzlet_ has quit (Read error: 104 (Connection reset by peer)).
07:59:59 -!- clog has quit (ended).
08:00:00 -!- clog has joined.
08:50:59 -!- nooga has joined.
08:51:02 -!- nooga has left (?).
08:51:06 -!- nooga has joined.
08:53:44 -!- puzzlet has quit (Read error: 104 (Connection reset by peer)).
09:07:14 -!- puzzlet has joined.
11:37:58 -!- nooga_ has joined.
11:46:23 -!- nooga_ has quit (Read error: 104 (Connection reset by peer)).
11:47:51 -!- puzzlet has quit (Read error: 110 (Connection timed out)).
11:56:04 -!- nooga has quit (Read error: 110 (Connection timed out)).
12:30:40 -!- nooga has joined.
13:03:50 <nooga> coding in befunge is like a game ;]
13:07:59 <fizzie> Especially the size-optimizing part.
13:09:55 <fizzie> You might want to see http://quux.befunge.org/befunge.html
13:10:36 <nooga> javascript interpreter
13:11:50 <fizzie> There's also the "quicksort with pretty colours" thing.
13:58:03 <nooga> maybe im making something bad
13:58:19 <nooga> but this js interpreter doesn't work well
14:05:10 <nooga> ip is moving in a funny way
14:07:10 <nooga> ill write my own interreter
14:07:20 <nooga> it will be much more funny
14:07:21 <fizzie> Hmm, strange. You sure you did the "configuration" part (dragging the boxes like the instructions say) correctly when you loaded the page? It seems to work for me.
14:07:29 <fizzie> Writing interpreters is fun.
14:07:48 <nooga> but when i do te configuration the ip frame is 3x3 pixels
14:08:18 <fizzie> Hmmm. Might be a browser incompatibility then. Works with firefox here.
14:08:40 <fizzie> Usually when I'm learning a new language the first thing I do is to write a befunge interpreter with it.
14:09:23 <fizzie> That's what I did with FORTRAN and Forth. And Haskell.
14:10:37 <nooga> befunge is much more interesting than bf
14:12:49 <nooga> my first program xD
14:14:37 <fizzie> Hmmm.. might be interesting to write a non-deterministic variant of befunge, with an added "fail" instruction that'd backtrack to the last ?.
14:21:51 <fizzie> Not that I'd know many who'd write anything "serious" with befunge.
14:24:24 <nooga> excuse me but i dont understand ;]
14:24:33 <nooga> my english is too limited ;)
15:00:39 -!- kpreid has quit.
15:14:42 -!- Keymaker has joined.
15:14:48 <Keymaker> "06:10:37 <nooga> befunge is much more interesting than bf"
15:18:56 -!- nooga has quit (Read error: 113 (No route to host)).
15:47:36 -!- Keymaker has quit ("Lhdss").
21:11:26 -!- nooga has joined.
21:12:03 <nooga> i wrote a befunge interpreter in turbo pascal lol :)
21:12:43 <nooga> my grandma as got old pc, i was eating dinner in my grandma's house, so i checked it out :P
23:23:44 -!- nooga_ has joined.
23:31:06 -!- nooga has quit (Read error: 113 (No route to host)).