00:00:00 --- log: started retro/13.01.10
00:29:38 --- quit: impomatic (Quit: http://corewar.co.uk)
01:53:58 --- join: harrison (~quassel@li89-226.members.linode.com) joined #retro
02:03:21 --- quit: harrison (Ping timeout: 246 seconds)
04:33:16 <erider> tangentstorm: I got the image to load but there are still issues with execution of retro internal stuff. I believe it is a semantics problem in my coding.  
04:33:37 <erider> semantic
04:34:51 <erider> I thinking about a new solution and recode the whole thing but I am still tracking down bugs 
04:38:47 <tangentstorm> erider: i was going to ask if you knew about ngarotest
04:39:39 <tangentstorm> http://code.google.com/p/retro-language/source/browse/#git%2Ftest%2Fngaro
04:40:48 <tangentstorm> If you implement the protocol described at the top of that file in your vm, you can test its behavior against the other implementations
04:41:28 <tangentstorm> currently py and c support the protocol in the main repo, and i've got versions for pascal and js in separate repos that haven't been merged back in yet
07:13:51 --- quit: erider (Ping timeout: 240 seconds)
07:20:36 --- join: impomatic (~digital_w@46.208.50.63) joined #retro
08:27:43 --- join: harrison (~quassel@li89-226.members.linode.com) joined #retro
08:58:00 --- quit: impomatic (Quit: impomatic)
08:58:26 --- join: kumul (~kumul@173.215.194.228) joined #retro
10:01:55 --- quit: karswell_ (Remote host closed the connection)
10:11:50 --- join: beretta (~beretta@cpe-107-8-120-84.columbus.res.rr.com) joined #retro
10:12:14 --- join: karswell_ (~coat@93-97-29-243.zone5.bethere.co.uk) joined #retro
10:40:27 --- quit: karswell_ (Remote host closed the connection)
10:50:45 --- join: karswell_ (~coat@93-97-29-243.zone5.bethere.co.uk) joined #retro
11:26:57 --- quit: karswell_ (Read error: Connection reset by peer)
11:37:14 --- join: karswell_ (~coat@93-97-29-243.zone5.bethere.co.uk) joined #retro
11:59:59 --- quit: beretta (Ping timeout: 240 seconds)
12:14:19 --- join: erider (~chatzilla@unaffiliated/erider) joined #retro
12:14:30 <erider> hi all
12:14:48 <tangentstorm> heya
12:15:26 <erider> hey tangentstorm how are things going 
12:15:40 <tangentstorm> pretty awesome :)
12:16:03 <erider> cool
12:16:37 <tangentstorm> i'm writing a little editor program. it's going to be scriptable in retro
12:16:58 <erider> that sounds neat 
12:17:12 <erider> it the core language in pascal 
12:17:17 <erider> is.. 
12:18:35 <tangentstorm> nope
12:19:07 <tangentstorm> i'm writing it in pascal at the moment but eventually it'll compile down to retro code and run on ngaro
12:19:58 <tangentstorm> so like when you press the key to "cut", it'll just execute a word in retro called "cut"
12:20:37 <tangentstorm> ^X or whatever will just be a trigger to run that word
12:20:48 <erider> ok so it is editor in pure retro 
12:20:51 <tangentstorm> probably using retro's new keybinding stuff that docl and crc made
12:22:12 <tangentstorm> well like i said it's pascal now, but i'm writing a pascal->ngaro compiler (retro pascal)... so if you make a procedure in pascal with no arguments, it'll be just the same as if you wrote the word in retro
12:23:26 <tangentstorm> i'm prototyping it in pascal and am about to be running it on the ngaro i wrote in pascal, but eventually you'll be able to run it in a browser using ngaro.js 
12:24:17 <erider> that is really neat 
12:26:33 <tangentstorm> http://i.imgur.com/YwsB9.png
12:26:41 <tangentstorm> well thank you :)
12:26:47 <tangentstorm> <link is the screenshot>
12:27:06 <tangentstorm> right hand side only. left side is emacs :)
12:27:10 <erider> you are an emacs guys ;-) 
12:27:42 <tangentstorm> yep!
12:28:01 <tangentstorm> did you see my message about ngarotest?
12:28:10 <erider> which one 
12:28:19 <tangentstorm> it might help you track down the bugs in the tcl vm
12:28:26 <erider> this morning 
12:28:28 <tangentstorm> er ngaro.tcl i mean :)
12:28:32 <tangentstorm> yeah
12:28:48 <tangentstorm> i don't know... i have no sense of time.
12:28:51 <erider> I saw you message and I replied 
12:28:56 <erider> your* 
12:29:15 <erider> your were asking about the status 
12:29:30 <erider> but I didn't see your reply if there was one 
12:29:48 <tangentstorm> 6:38:07 tangentstorm | erider: i was going to ask if you knew about ngarotest  
12:29:54 <tangentstorm> 06:39:00 tangentstorm | http://code.google.com/p/retro-language/source/browse/#git%2Ftest%2Fngaro 
12:30:00 <tangentstorm> 06:40:09 tangentstorm | If you implement the protocol described at the top of that file in your vm, you can test its behavior against the other implementations
12:30:08 <tangentstorm> 06:40:48 tangentstorm | currently py and c support the protocol in the main repo, and i've got versions for pascal and js in separate repos that haven't been merged back in yet
12:31:07 <tangentstorm> b
12:32:01 <erider> ah ok I didn't see that 
12:32:51 <erider> I am working pass get so of the basics stuff working. It loads the image fine but doesn't do much else :-( 
12:33:43 <tangentstorm> this just tests the behavior of each individual opcode
12:34:05 <tangentstorm> once you have those working, you can test the devices with the normal retro tests
12:34:29 --- quit: karswell_ (Read error: Connection reset by peer)
12:35:12 <tangentstorm> the idea behind ngarotest is it'll generate a tiny custom image for each test... then you load that image and dump ram and the two stacks
12:35:18 <tangentstorm> after it runs i mean
12:35:40 <tangentstorm> so you can make sure that  a particular set of instructions puts the vm in the right state
12:35:58 <tangentstorm> and there are tests defined for each of the opcodes
12:36:37 <erider> does it feed it into the implementation of ngaro
12:36:43 <tangentstorm> actually the /mod opcode test doesn't check that division rounds the right way with negative numbers, but all the others have pretty decent tests
12:37:37 <tangentstorm> not sure i understand your question
12:37:45 <tangentstorm> here's an example: http://code.google.com/p/retro-language/source/browse/test/ngaro/ngarotest.py#221
12:38:15 <tangentstorm> it assembles  '1234 dup'  to  LIT 1234 DUP ... so a 3-cell image.
12:38:30 <tangentstorm> you make your VM run that image, then dump state.
12:38:35 <erider> its testing the image
12:38:45 <erider> ah ok 
12:38:55 <tangentstorm> then it checks that the stack was [1234 1234]
12:39:09 <erider> then I run the image that it creates against my version of ngaro 
12:39:17 <erider> ok I follow 
12:39:17 <tangentstorm> and if not, it'll say   "ERIDER DOESN'T EVEN KNOW WHAT DUP MEANS! HA HA!"
12:39:28 <tangentstorm> :)
12:39:36 <erider> lol 
12:40:34 * erider just wget the py file
12:44:04 <erider> it makes a lot of img files 
12:44:44 --- join: karswell_ (~coat@93-97-29-243.zone5.bethere.co.uk) joined #retro
12:48:07 <tangentstorm> yeah
12:48:11 <erider> tangentstorm: what if you don't get any out from the image 
12:48:25 <tangentstorm> the test will fail
12:48:47 <tangentstorm> like right now, since you haven't implemented the protocol, itshould say "ran 32 tests. 30 failures" or something
12:48:52 <erider> I got nothing on the add.img 
12:49:34 <erider> oh you are not suppose to load the image into ngaro 
12:49:48 <tangentstorm> erider: yes, but there's no output to the screen
12:49:56 <tangentstorm> that's why you have to implement the code to dump the stacks 
12:50:24 <tangentstorm> you dump the stacks and the ram (so you can test the write-to-ram opcode)
12:51:26 <erider> oh 
12:51:33 <erider> I follow now 
12:52:00 <erider> I have to setup a unit test for my version 
12:55:08 <tangentstorm> nope
12:55:17 <tangentstorm> you just implement the protocol
12:55:27 <tangentstorm> the tests are the same because they follow the ngaro spec
12:55:34 <tangentstorm> one sec
12:55:47 --- quit: karswell_ (Remote host closed the connection)
12:58:11 <tangentstorm> http://bazaar.launchpad.net/~tangentstorm/retro-language/docwork/revision/402#vm/complete/retro.py
12:58:22 <tangentstorm> that shows what i had to change in retro.py to get it to accept the protocol
12:59:15 <tangentstorm> mostly the bigger green blocks towards the bottom
13:00:11 <tangentstorm> bascially you implement --image <filename> (which it sounds like you already have), and --dump which is the little block on line 399 there
13:00:45 <tangentstorm> and that's it.
13:01:15 <erider> ok 
13:02:06 <tangentstorm> also add an entry to the makefile so you can say   make test.tcl  or whatever
13:04:21 <erider> so I need to make a --dump cli option 
13:06:05 --- join: karswell_ (~coat@93-97-29-243.zone5.bethere.co.uk) joined #retro
13:10:44 <tangentstorm> yep
13:12:16 <erider> ok 
13:13:18 <erider> how long does the test take tangentstorm 
13:14:02 <tangentstorm> a few seconds
13:14:26 <tangentstorm> check out the whole repo and just run make test in that directory... it'll run the c and python ones very quickly
13:14:44 <tangentstorm> and then probably blow up because i haven't got the pascal one in the repository yet :)
13:15:58 <tangentstorm> of course it kind of depends on the speed of your implementation :D
13:16:52 <erider> NGARO_CMD = tclsh /home/erider/Public/tclstuff/ngaro.tcl
13:16:54 <erider> ..
13:17:20 <erider> its stuck there :-( 
13:19:37 <erider> ok no worries I know what's wrong 
13:20:24 <erider> I will play with that later 
13:25:54 <tangentstorm> oh. sorry i missed that.
13:46:28 --- quit: kumul (Read error: Connection reset by peer)
14:08:45 <erider> tangentstorm: what else is going on 
14:13:48 <tangentstorm> that's pretty much it
14:15:07 <tangentstorm> i've been working on this course/language/tool/thing for a year and i have all the ideas in place and now i'm just straight up coding all day to get it out the door
14:15:25 <tangentstorm> and hanging out in irc blabbering about i guess :D
14:16:21 <erider> ah ok 
14:16:39 <erider> I am redoing parts of the code 
14:49:56 <harrison> have you ever lost a buch of code due to a hard disk failing or whatever (before the Cloud obv) and thought that it would be painful to rewrite from memory but it turned out to be not only easy enough but actually a good thing?
14:58:26 <erider> It would definitely helps one memory 
15:00:10 <erider> harrison: did that help 
15:00:17 <erider> happen 
15:18:51 --- quit: karswell_ (Remote host closed the connection)
15:23:44 <harrison> yes it is a formative crisis
15:23:57 <harrison> such as comes but once in lo these many moons
15:29:08 --- join: karswell_ (~coat@93-97-29-243.zone5.bethere.co.uk) joined #retro
15:29:36 --- join: ncv (~quassel@89.35.216.197) joined #retro
15:29:37 --- quit: ncv (Changing host)
15:29:37 --- join: ncv (~quassel@unaffiliated/neceve) joined #retro
15:43:38 --- nick: tangentstorm -> tangentzzz
15:50:55 --- join: kumul (~kumul@173.215.194.228) joined #retro
16:03:15 --- join: ncv_ (~quassel@89.35.216.197) joined #retro
16:50:20 <erider> hi all 
16:54:07 --- quit: ncv_ (Ping timeout: 276 seconds)
17:58:02 --- join: beretta (~yaaic@cpe-107-8-120-84.columbus.res.rr.com) joined #retro
18:06:52 --- join: beretta_ (~beretta@cpe-107-8-120-84.columbus.res.rr.com) joined #retro
18:09:34 --- quit: ncv (Remote host closed the connection)
19:39:23 --- quit: karswell_ (Remote host closed the connection)
19:49:40 --- join: karswell_ (~coat@93-97-29-243.zone5.bethere.co.uk) joined #retro
20:10:39 --- quit: karswell_ (Remote host closed the connection)
20:23:55 --- join: karswell_ (~coat@93-97-29-243.zone5.bethere.co.uk) joined #retro
20:36:04 --- quit: karswell_ (Remote host closed the connection)
20:46:27 --- join: karswell_ (~coat@93-97-29-243.zone5.bethere.co.uk) joined #retro
20:55:54 --- quit: karswell_ ()
21:09:53 --- join: karswell (~user@93-97-29-243.zone5.bethere.co.uk) joined #retro
21:38:01 --- part: beretta left #retro
21:56:32 --- nick: tangentzzz -> tangentstorm
22:01:25 --- quit: tangentstorm (Quit: WeeChat 0.3.2)
23:41:47 --- join: tangentstorm (~michal@108-218-151-22.lightspeed.rcsntx.sbcglobal.net) joined #retro
23:55:45 --- quit: kumul (Read error: Connection reset by peer)
23:59:59 --- log: ended retro/13.01.10