00:00:00 --- log: started retro/13.02.06
00:39:55 --- quit: crcx (Ping timeout: 244 seconds)
02:16:15 --- join: crcx (~crcx@li125-93.members.linode.com) joined #retro
04:32:06 --- nick: tangentsleep -> tangentstorm
08:31:03 --- join: kumul (~Kumool@c-76-26-237-95.hsd1.fl.comcast.net) joined #retro
10:56:05 --- join: ncv (~quassel@79.114.79.37) joined #retro
10:56:05 --- quit: ncv (Changing host)
10:56:05 --- join: ncv (~quassel@unaffiliated/neceve) joined #retro
12:05:12 --- join: kbmaniac_ (~dave@host86-157-24-246.range86-157.btcentralplus.com) joined #retro
12:05:13 --- quit: kbmaniac__ (Read error: Connection reset by peer)
12:05:49 --- join: dessos (~derk@c-174-60-176-249.hsd1.pa.comcast.net) joined #retro
12:26:02 --- join: Mat2 (~claude@91-65-144-133-dynip.superkabel.de) joined #retro
12:26:09 <Mat2> Hi @ all !
12:26:38 <tangentstorm> hey Mat2 :)
12:26:46 <Mat2> hi tangentstorm !
12:27:10 <tangentstorm> what are you up to today?
12:27:45 <Mat2> I'm working on the parser for retro
12:28:45 <tangentstorm> to parse one word at a time, or to parse higher level things like  [ a ] [ b ] if   ?
12:31:08 <Mat2> the type system
12:31:52 <Mat2> and I have to make a decision: Should I rely on posix threads or the traditional fork mechanism ?
12:32:23 <tangentstorm> ... beats me. i don't really use either.
12:36:38 <Mat2> as I see it *nix fork mechanism is very easy to handle because it duplicate the whole application state
12:37:22 <Mat2> where posix threads (and processes) are more flexible (and difficult to handle)
12:37:50 <Mat2> performance wise, it seems I have the choice between pest and cholera
12:42:42 <Mat2> ok, my decision is just to use the traditional fork mechanism
12:43:41 <Mat2> (and hope there will exist a good compatibly wrapper for Windows systems)
12:50:07 --- join: kbmaniac (~dave@host86-157-24-246.range86-157.btcentralplus.com) joined #retro
12:53:11 <tangentstorm> what do you need to fork? :)
12:55:25 --- join: ncv_ (~quassel@79.114.83.87) joined #retro
12:55:51 <Mat2> only the intrinsic fork macro of the std. C library (these function is part of the linux and BSD kernel functionality)
12:57:02 <Mat2> on Windows I do not know the situation, but it should exist some kind of "WinCreateProcess" function somewhere
12:58:01 --- quit: ncv (Ping timeout: 252 seconds)
12:58:09 <Mat2> (I bet there exist dozens of such functions in Windows)
13:05:16 --- quit: kbmaniac (Ping timeout: 246 seconds)
13:06:58 <tangentstorm> :) probably
13:13:43 <crcx> Mat2: on Windows, CreateProcess or CreateThread
13:13:53 <Mat2> thank you
13:32:38 --- quit: impomatic (Quit: impomatic)
13:52:04 --- quit: ncv_ (Remote host closed the connection)
14:31:13 <Mat2> ciao
14:31:20 --- quit: Mat2 (Quit: Verlassend)
14:53:25 <erider> hi
15:03:41 <crcx> Hi erider
15:21:06 <erider> hi crcx 
15:21:47 <erider> hey do you know how to split a binary file into string like "\x41" 
15:22:12 <erider> using bash 
15:24:53 <erider> nevermind I can use xxd 
15:29:01 <erider> crcx: are you on the ipad? 
15:59:41 <crcx> Yes, on ipad
16:00:31 <erider> yeah that is what I thought
16:00:31 <crcx> Just finishing up the parable decompiler (php implementation):  http://rx-core.org/parable/play/dumpImage.php
16:01:55 <tangentstorm> what do the numbers inside the brackets mean?
16:02:08 <tangentstorm> like the 402 in [ `402 ] 'memory.store' define
16:03:34 <erider> opcode most likely 
16:06:27 --- join: kumool (~Kumool@c-76-26-237-95.hsd1.fl.comcast.net) joined #retro
16:08:21 <tangentstorm> i thought there were 64 or so opcodes in the parable vm?
16:08:31 <tangentstorm> maybe a call to a quote?
16:09:07 --- quit: kumul (Ping timeout: 248 seconds)
16:09:21 --- join: kumul (~Kumool@c-76-26-237-95.hsd1.fl.comcast.net) joined #retro
16:09:45 <tangentstorm> have you guys seen mako?
16:09:59 <tangentstorm> https://github.com/JohnEarnest/Mako
16:10:34 <tangentstorm> he's got some pretty awesome games written in forth, as well as some audio stuff.
16:10:41 <erider> tangentstorm: I don't know but that was my guess 
16:11:03 <tangentstorm> all of it is running on a VM that's not *too* different from ngaro...
16:11:41 <tangentstorm> but he has a really nice system for sprites and sound
16:12:20 --- quit: kumool (Ping timeout: 264 seconds)
16:12:21 <erider> tangentstorm: did you play the pong game 
16:12:26 <tangentstorm> i'm kind of wanting to create a synthesis of the two
16:12:38 <tangentstorm> and maybe some of the sliced memory stuff from parable too..
16:13:05 <tangentstorm> yes. definitely my least favorite, with that scary red screen :)
17:03:41 <crcx> Opcodes are roughly grouped, not strictly numerical
17:04:17 <crcx> See http://rx-core.org/parable/play/src/bytecode.coffee
17:35:14 <tangentstorm> oh. cool :)
17:42:08 <crcx> http://rx-core.org/parable/play/doc/html/bytecode.html has some docs on the bytecode stack usage
18:13:52 <tangentstorm> that's pretty clean
18:15:01 <tangentstorm> push comment?
18:15:22 <tangentstorm> for what? manipulating source code?
18:50:56 <crcx> Comments get tracked so parable's decompiler can reconstruct the source as closely as possible
18:55:47 <tangentstorm> oh. nice :)
19:25:29 --- join: kumool (~Kumool@c-76-26-237-95.hsd1.fl.comcast.net) joined #retro
19:29:08 --- quit: kumul (Ping timeout: 264 seconds)
20:16:09 --- quit: kumool (Quit: Leaving)
23:59:59 --- log: ended retro/13.02.06