% mdiep has left mdiep!~matt@c-24-18-232-4.hsd1.wa.comcast.net
% allison has joined #parrotsketch
<obra> hi!
<obra> Oh. clock here is 10 minutes fast.
<obra> heh
% allison has left allison!~chatzilla@sub17-30.member.dsl-only.net
% allison has joined #parrotsketch
% woggle has joined #parrotsketch
<obra> Are folks all here?
<leo_> hi @all
<particle> howdy
% coke has joined #parrotsketch
<allison> hi
<obra> hey folks
<chip> hi
<obra> let's get running.
<obra> allison: How's things?
<allison> I've been a bit absorbed in $paying_job the past couple of days.
<allison> but I did make significant progress on Punie last week
<allison> passed the first complete test file
<allison> (Perl 1 test file)
% chromatic has joined #parrotsketch
<obra> Very nice. which one?
<allison> I'm working now on short-ciruiting operators
<allison> base.if, IIRC
<allison> fairly short, but Larry is almost as devious in his test files as Guido is in his benchmarks 
<allison> each file requires a fairly large collection of features
<allison> the short-ciruiting operators should allow me to pass another test file
<allison> I think arrays, hashes and subs are next
<allison> with those, people will be able to write a good bit of working code in Punie
<allison> I've also been preparing for YAPC talks
<allison> EOR
<obra> chip: What's new?
<chip> Well, I'm obviously not gonna make all PDDs reviewed by YAPC
<chip> OSCON, it could happen :-)
<chip> I thought exceptions would be an easy nut to crack, but, well, not so much.  The Common Lisp condition system can't work without an additional feature or two (I'm trying to hold it to one)
<chip> I've decided to revert my .{begin,end}_eh static-description-of-exception-ranges idea, for two reasons: (1) it may make life harder for some dynamic languages like Lisp, (2) it's turned out to be a can of bikeshed paint
<chip> And of course YAPC presentation is in progress as well
<chip> Anyone who wants to talk continuations, we can do it here, but I think we may as well adjourn to #parrot after
<chip> EOR
<obra> Cool.
<obra> leo_: how's stuff?
<leo_> * the usual code cleanup & bugfixes for:
<leo_> * release 0.4.5
<leo_> * checked (again) the STM branch - looks all really good and sane
<leo_> * re Charle's mail for thread creation: I think the flags argument could
<leo_>   specifiy the amount of what is to be cloned similar to clone(2)
<leo_> ,end
<obra> congrats on the release. 
<obra> clockwork++
<leo_> thx
<obra> particle: you around?
<particle> yep
<obra> What's up?
<particle> two four letter words blocking me on parrot milestones
<particle> yapc, and time.
<particle> those are somewhat correlated
<particle> so, nothing to report.
<obra> ok. at YAPC, we'll work on time ;)
<obra> coke, you around?
<coke> no.
<obra> Ok. No coke today ;)
<obra> pepsi?
<coke> ah. back. 
<obra> Ok. what's exciting?
<coke> work  is hellish. in con call right now. haven't done presentation yet. pmi has gone missing. 
<coke> no fun, no time see you next week bye.
<obra> take care
<obra> (I believe patrick is in the middle of buying a house)
<obra> chromatic: how's pheme? (And other stuff?)
<chromatic> Leo's GC patch fixed it, so I cleaned up the distro and added a couple of files his checkin missed.
<chromatic> I spent last week working on my talks, so I haven't made any further progress.
<chromatic> I am seeing a MANIFEST failure about a Tcl runtime file; can't really reproduce it from the repo though.
<chromatic> I have an easy workaround though.
<chromatic> I'll try to add a Pheme special form, maybe cond, in the near future.  That ought to go quickly; I think the only barrier right now is my time.
<chromatic> That's all.
<obra> woggle: you around?
<woggle> Yes.
<obra> how's soc-life?
<woggle> Okay.
<woggle> I added read-only value support to the STM branch.
<woggle> This is done by just swapping vtables. Read-only values are otherwise indistinguishable.
<woggle> As a side effect the STM branch supports annotating vtable operations in vtable.tbl relatively generally.
<woggle> I've started work on some multithreaded STM tests so I have something to make work, but it's not at release quality yet.
<woggle> I've also been looking at removing the threading interface a bit from history, see my list post.
<woggle> EOR
<woggle> s/release/SVN/
<leo_> woggle: np ci early, ci often
<obra> (Is there a reason to not check in to your branch?
<obra> svn lets you roll back. check in all the time ;) It does make life better. and other people send patches.
<woggle> I'd prefer that the file at least run and fail before ci it. (;
<obra> I'll defer to leo on this one (or chip) or really anyone else for policy.
<obra> anyone I missed?
<leo_> well, as said above ( a log line can state: not finished ... )
<chip> [On a branch, the people who are looking at the branch can set whatever policy they're comfortable with.  Personally I'm always afraid that a local disk crash will lose my work.]
<leo_> but it's not really that important in the branch - its basically woggle's policy ;) 
<obra> ok. I think that's everybody. So, what, (besides YAPC and time) are folks blocking on? Just shout things out.
<obra> (Do type them after that, though)
<particle> pmichaud's time, but i think that'll be solved for will and i at yapc
<chip> EH spec depends on details of continuations, so I'm learning that.  Chat with leo should help.  That's what I'm planning for #parrot
<chromatic> I have an upcoming job where the working solution appears to be embedding Parrot.
<chromatic> I'll be exploring the embedding interface soonish.
<chip> BTW, Larry explained something nicely WRT Perl 6 warn() throwing an exception like fail().  I was going to object that a fail() handler could resume and that would break things, but then I realized that if you outlaw everything that could break things, you're pretty much writing 1-2-3 macros
<chip> {besides, it's possible to arrange for some exceptions to include a continuation while others don't ; the latter would actually be impossible to resume}
<leo_> yep - basically any exception thrown from C is un-resumable
<chip> well, that too :-)
<obra> ok. next up, the hackathon.
<obra> What can be done to help make the hackathon useful and productive?
<particle> more granular list of todos, whether in rt or not. especially, a low-hanging-fruit list.
<particle> (that's for the non-core-committers)
<chip> Hm.  I'd like to give everyone a "leave this and come back to it" button for runaway arguments^Wdiscussions
<chip> What's the physical arrangement going to be like?
<particle> an event-driven tangent yield button? neat.
<chip> One big room (like Toronto) doesn't seem ideal to me.  Working groups rock.
<chip> (esp. if they can only vaguely hear each other)
<obra> c1;2chI'm told  that we have a bunch of lounges.
<chip> excellent
<particle> is there a 'must hack' list of topics?
<obra> I hear rumors patrick is coming armed with one
<obra> particle: would it be worth having an rt-a-thon the first day to get things clenaed up and fleshed out where they're thin?
<particle> sure, you can put me in for that
* chip likes the RT-a-thon, despite his personal ticket list
<obra> I may deputize you to corral folks for that, as you're much better versed parrot RT it than I am
<obra> I'll likely do a supermarket run on thursday to get folks hacking.
<obra> Pizza will be ordered, etc.
<particle> okie
<obra> "I think I can get my employer to sponsor a day or two of pizza"
<obra> Anyone have anything else for today?
<chip> nope
<obra> No parrotsketch next week due to yapc
<obra> I'll see lots of you at the hackathon
<chip> yay
% chromatic has left chromatic!~chromatic@sub17-30.member.dsl-only.net
<obra> &
% particle has left #parrotsketch
% woggle has left #parrotsketch
% PerlJam has joined #parrotsketch
% coke has left coke!~wcoleda@host-69-95-19-3.roc.choiceone.net
% coke has joined #parrotsketch
% coke has left coke!~wcoleda@cpe-72-228-52-192.nycap.res.rr.com
% coke has joined #parrotsketch
% coke has left coke!~wcoleda@cpe-72-228-52-192.nycap.res.rr.com
% coke has joined #parrotsketch
% coke has left coke!~wcoleda@cpe-72-228-52-192.nycap.res.rr.com
% mdiep has joined #parrotsketch
% allison has left allison!~chatzilla@sub17-30.member.dsl-only.net
% coke has joined #parrotsketch