% particle has joined #parrotsketch
<chip> I'm going to be hitting the tunnel just when the meeting starts today, sadly.  On the good side, this won't result in a shorter report, as I was on vacation from all typing this week
<chip> I know I have a couple of pending requests (understatement alert klaxon sounds here)
<chip> specifically, namespaces and named parameters.
<obra> also, the milestones update ;)
% allison has joined #parrotsketch
% leo has joined #parrotsketch
<obra> 'morning, guys
<mdiep> good afternoon :-)
<allison> g' morning
<leo> hi all
<obra> shall we get kicking?
<obra> chip: you still here?
<obra> if not, mdiep, what's new?
<mdiep> we're still waiting for leo to fix our segfaulting code :-)
<mdiep> I thought the library duplication issue would do it, but apparently not
<mdiep> overall, not much happened this week in the land of tcl
<mdiep> but I did manage to send my final namespace draft to chip. things are in his hands now.
<mdiep> we're blocking on those two bits
<mdiep> and that's about it
<mdiep> ^D
<obra> Ok. you having fun?
<obra> (Answer when you return)
<obra> leo: what's new?
<leo> - converted library loading (loadlib, load_bytecode) to use STRING* for filenames
<mdiep> I'm starting to have fun again, yes. I began looking at the PGE code this week and am looking at refactoring some of the cruft in Tcl. It feels good to be in actual code again.
<leo> - tcl tests fine on x86 and x86_64 and fails on darwin (somtimes, mostly)
<leo> - new code to prevent load_bytecode 'duplicate'
<leo> - helped folks a bit with shootout benchmarks
<leo> - improved parts of parrot speed by a factor of 2 or more
<leo> that's all
<obra> ok. whatcha blocking on?
<leo> just my time
<leo> (and I've fun ;-)
<obra> :)
<obra> allison?
<allison> extending punie to handle more syntax
<allison> so far, multiple statements in a file
<allison> and printing things other than a single digit
<allison> Patrick patched PGE for me so it will now capture the string inside balanced brackets
<allison> I'll update punie to use that next.
<allison> also most of the way to using a PGE grammar compiled down to PIR, instead of compiling it at runtime
<allison> (getting TGE to a point where it can do the same is on my roadmap)
<allison> that's all
<obra> ok. are you blocking on having fun?
<allison> er... I'm having fun, anyway :)
<obra> :P
<allison> not blocking on anything at the moment (Patrick has been really fast at responding to any questions or problems I have)
<obra> can you have the problem that patrick's not here ;)
<allison> email's good enough for most things :)
<obra> aw
<obra> ok. so. chip said that he'd been on a break from typing this past week, just before the meeting started
<obra> so. questions?
<obra> oh. wait
<obra> particle: you here?
<particle> 'lo all
<obra> Last week I asked particle to join us this week.
<obra> And it completely slipped my mind, likely due to lack of coffee
<obra> So, hiya.
<obra> Want to give a rundown on who you are and what you do for the logs?
<particle> particle, aka jerry gay, and i'm responsible for the parrot test suite.
<particle> i've started reorganizing it. all tests live under t/ now.
<particle> there's more to do, like adding support in the harness for running both perl and pir tests. this will come soon.
<particle> i've taken a bit of a break from that right now in order to decrease entropy in parrot directory structure
<particle> which is going very well, and is nearly complete. this will reduce top-level directories from 30+ to 15.
<particle> that's me, and what i do.
<obra> Cool. What's your past week looked like (in terms of parrot)
<particle> directory reorg. i've moved a bunch of dirs around, with minimal trouble.
<particle> noticed tcl's failing to build on win32
<particle> it's a pbc_merge issue, but i haven't figured out the win32 dubugging tools yet.
<obra> *nod* 
<obra> are there things you're working on that other folks could be helping out with?
<particle> i don't need any special assistance from folks here atm. in general, tests are always welcome.
<obra> It's also that testing is often one of the easiest ways to rope in newbies ;)
<obra> but cool. welcome.
<obra> questions for Jerry?
% allison is now known as chromatic
<particle> heh.
* chromatic will report now
<particle> BTW: parrot -Ofun -Onoprofit dir_reorg.pir
<obra> hey chromatic.
<chromatic> I rewrote a sucky test because it was failing, and that revealed the error so we fixed it.
<chromatic> I suspect there are plenty of other tests that use ok( $foo == $bar, $name ) that should instead use is( $foo, $bar, $name )
<chromatic> There's some low-hanging fruit for recruiting new "don't make me write C!" programmers.
<chromatic> Otherwise, I had a flash of insight to the pure-PIR tests in t/ext/ or wherever last night, but haven't written any code yet.
<chromatic> Soon.
<chromatic> ^D
% chromatic is now known as allison
<obra> ok
<obra> questions?
<obra> or do I get to gavel the meeting closed?
<particle> one thing
<particle> i noticed the milestones doc seems out of date wrt parrot milestones
<particle> or, at least, that it could use some more text
<obra> ok. what more text?
<obra> and yes, chip owes me updates.
<particle> okay, the updates by chip is what i mean.
<particle> wasn't sure if that was in the works, or if it needed a pair of hands
<allison> do you mean it needs status updates? or changes in the planned goals?
* obra presumed status updates
<particle> status updates
<obra> if you know what's already done, shoot me mail and I'll update.
<mdiep> obra: there was a question posted to p6l a few weeks ago about the status of ponie. that could really use answering.
<obra> I've been having some trouble pinning chip down to find out what's up.
<obra> mdiep: I'm well aware. an answer is in the works.
<mdiep> excellent.
<obra> and. failing anything else, I'll see y'all next week
<leo> see you - bye
% allison has left allison!~allison@sub17-30.member.dsl-only.net
% particle has left #parrotsketch
% leo has left #parrotsketch