% particle_ has joined #parrotsketch
% particle has left particle!~particle@c-24-19-12-148.hsd1.wa.comcast.net
% particle_ is now known as particle
% pmichaud has joined #parrotsketch
% particle has left particle!~particle@144.81.84.205
% particle_ has joined #parrotsketch
% particle has joined #parrotsketch
% chromatic has joined #parrotsketch
% bernhard has joined #parrotsketch
<particle_> hi all! coke's unavailable today, so i'll be running the show. who's here?
<pmichaud> here
<bernhard> me too
* chromatic waves all of his fingers
% allison has joined #parrotsketch
<particle_> okay, let's try to catch allison off guard, and ask for her status first :)
<allison> (not pretyped)
<allison> I've been working on the PMC PDD
<allison> and on the --gc=libc configure problem
% smash has joined #parrotsketch
<allison> That's all I can think of at the moment
<allison> EOR
<particle_> bernhard?
<bernhard> Applied patches from Dave Rolsky, Mike Mattie, Mark Glines.
<bernhard> Removed gen_manifest_skip.pl
<bernhard> Looked at languages/lisp 
<bernhard> .eor
<particle_> chromatic?
<chromatic> I fixed some bugs.
<chromatic> I cleaned up some code.
<chromatic> I've been looking at open patches and open bugs, and could use some help categorizing and classifying them.
<chromatic> I still plan to do as much as I can on PDD15 by the release.
<chromatic> I can't make this Bug Day, however.
<chromatic> .end
<particle_> coke says, "06I have no report, except perhaps "I'm trying to get NaN and Inf working in partcl"01
<particle> pmichaud?
<pmichaud> * After looking at S05 changes, Larry's standard perl6 grammar, the improvments to Parrot's object/class system, and based on discussions with particle and obra, I've decided that we need a somewhat different approach to the parse -> PAST stage of compilation
<pmichaud> * In particular, I'm currently designing a small intermediate language to make it easier to build ASTs from the parse phase
<pmichaud> * The language will be similar in concept to (but perhaps not entirely identical to) the "miniperl6" language that is being developed in Pugs
<pmichaud> * I.e., it'll look like a subset of Perl 6
<pmichaud> * When completed, it should sharply reduce the amount of PIR/Parrot knowledge that people need in order to build or hack on compilers
<pmichaud> * Particularly the perl6 compiler
<pmichaud> * I'll start by building and using this for languages/abc, as a demonstration and illustration of the concepts
<pmichaud> * Then we'll update perl6 to match, and open things up for widespread hacking
<pmichaud> * I expect this to happen very quickly, as we already have reasonable tools for building small languages in Parrot.  Now we just need tools for building the big ones.  :-)
<pmichaud> * Summaries and progress reports should start appearing on perl6-compiler, to increase the transparency of the process
<pmichaud> EOR
<particle_> my turn:
<particle> ~ simplifying Exporter's interface a bit, expect a commit RSN
<particle> ~ big thoughts, few commits. i expect this to change soon
<particle> ~ i'm really annoyed at the inability to subclass pmc's in pir. i know it's changing, and i'm looking forward to it
<particle> ~ building a new system that should give me more flexibility in parrot configurations
<particle> ~ a few patches on my TODO list for review
<particle> .end
<particle> anyone else have a report?
<pmichaud> . o O ( we STILL cannot reliably subclass PMC's in pir?  I thought that was being fixed... )
<particle> super doesn't work. i'll provide an example on list after i commit my Exporter changes
<chromatic> Modulo some vtable questions, I've done it fairly well.
<chromatic> Oh.  super has never worked.
<particle> needs fixed.
<particle> who's blocking, or not having fun?
<pmichaud> I'm unblocking
* particle cheers
% tewk has joined #parrotsketch
<allison> pmichaud: that's part of the revamp of objects and PMCs, still in progress
<pmichaud> allison: okay, for some reason I thought it was farther along.  No big worry, I can continue to work around
<particle> okay, we need focus for this release. anyone care to suggest things, go ahead.
<chromatic> PDD 15
<particle> yeah, sounds good to me.
<particle> how can we assign/track the work? if only we had a system for that....
<chromatic> It would be nice to categorize all of the open patches as well.
<particle> speaking of which, you need some rt access, dontcha?
<chromatic> To close tickets, yes.
% mdiep has joined #parrotsketch
<particle> i've msg'd ask, maybe he can help
<particle> mdiep, have status today?
<mdiep>  - Changed Parrot_get_vtable_index to use a binary search instead of a linear search
<mdiep>     - Optimized Parrot runs Tcl's make test in 8m50s instead of 12m8.5s
<mdiep>  - Closed some more patches in the queue
<mdiep>  - Converted some code to use :vtable
<mdiep> EOR
<pmichaud> mdiep++
<mdiep> particle noted that parrot's make test actually takes longer with my patch, but both PGE's and Tcl's make test are faster.
<particle> let's turn to open discussion. i have a question for allison
<particle> allison, do you have a revised timeframe for the pmc pdd draft?
<allison> last friday?
<tewk> is there a list of PDD15 open tasks?
<allison> I plan on working on it today
<mdiep> failing tests for PDD15 would be great too
<allison> tewk: what I was planning to do next was fork the current objects tests, and run them on the new implementatio
<tewk> ok
<particle> we have a wiki page with some pdd15 tasks, but i think it's time to track them in rt now
<allison> it means replacing 'newclass' in the tests with a more direct call to the new Class
<allison> really, anyone could do that, it doesn't have to be me
<allison> that'll give us a whole pile of failing tests to satisfy
<particle> re pdd15: first step should be to analyze what's done already
<tewk> As for file of the week, I checked in some comments to object.c last week.
<allison> tewk: great, thanks!
<tewk> I'll fork the pdd15 tests today.
<allison> particle: my understanding of what's done, we have a complete implementation of the core Class and Object PMCs
<allison> what we're lacking is the integration into Parrot
<allison> the opcodes currently call the old style ParrotClass and ParrotObject
<particle> we're lacking some tests
<particle> s/some/many/
<allison> and src/objects.c has a number of hard-coded references (directly poking in the internals) to the old implementation
<allison> particle: that's the idea of forking the old test suite
<allison> but, really I think the old test suite needed extensions too
<particle> when you say fork, do you mean branch?
<tewk> I think we mean duplicate with a new "newclass" opcode.
<allison> not branch the repository, but create separate tests, starting with the existing test
<particle> okay, gotcha
<allison> tewk: yeah
<allison> we need to be able to run the full tests for both old and new implementations
<allison> (for the refactor approach)
<particle> agreed, until old is ripped out
<tewk> old tests will go out with old impl, when the time comes.
<allison> aye
<particle> i'm pretty sure ops/methods like 'inspect' and 'inspect_str' are incomplete
<allison> particle: ah, very likely
<allison> separate question, is anyone else having trouble with: http://svn.perl.org/viewcvs/parrot/
<pmichaud> allison: failed for me now, yes
<mdiep> same here
<particle_> wasn't that taken down on purpose?
<pmichaud> but http://svn.perl.org/parrot works
<chromatic> http://svn.perl.org/viewcvs/parrot/ worked for me.
<particle_> we're svn now, not cvs
<allison> particle, I was using it this morning
<particle_> huh.
<allison> particle: yeah, viewcvs works on svn
<mdiep> now it works for me again.
<chromatic> You're all mimics.
<allison> ah, me too, so just a 10 minute outage
<bernhard> And rsync was/is broken.
<bernhard> rsync -av --delete cvs.perl.org::parrot-HEAD parrot
<allison> do we have a ticket in the admin queue for that?
<mdiep> I tried forwarding a ticket in the parrot queue to the webmaster queue, but I don't think it went through.
<mdiep> that was a few weeks back.
<bernhard> RT #42554
<allison> ViewVC is down again
<particle> anything else sketchy to report, or shall we adjourn to #parrot?
<chromatic> Who can make it to Bug Day on Saturday?
<pmichaud> I'm iffy
<particle> not likely
<pmichaud> saturday there are a number of family events taking place all day
<mdiep> I'm not sure. I'm moving this weekend.
<allison> I'll be there
<bernhard> only for a couple of hours
<chromatic> Hm.  I don't want to move the release, but should we move the Bug Day or skip it this time?
<pmichaud> I'll see if I can cover early morning before the rest of the household is up
<particle> if it's not advertised, it's unlikely many will show up :)
<particle> if all goes well this week, i'll have some new platforms updates
<pmichaud> I'm okay on either moving or skipping bug day for this month, fwiw
<chromatic> It would be nice to have people there, but if most of us can't make it I'm less keen on advertising it.
<particle> sounds like it'll be a quiet day, then. okay.
<tewk> I'll be around in the morning and late evening (MST)
<particle> let's wrap up. everybody remember to comment your code! see you next week.
<pmichaud> see you all next week
% chromatic has left #parrotsketch
% allison has left #parrotsketch
% bernhard has left bernhard!~bernhard@p549A2928.dip0.t-ipconnect.de
% particle_ has left particle_!~particle@144.81.84.205
% particle has left particle!~particle@144.81.84.205
% particle has joined #parrotsketch
% particle has left particle!~particle@144.81.84.150
% particle has joined #parrotsketch