% avar has left avar!~avar@dsl-228-236.hive.is
% avar has joined #parrotsketch
% particle has left particle!~particle@144.81.84.216
% particle has joined #parrotsketch
% avar has left avar!~avar@dsl-228-236.hive.is
% avar has joined #parrotsketch
% particle has left particle!~particle@144.81.84.216
% particle has joined #parrotsketch
% PerlJam has joined #parrotsketch
% mdiep has joined #parrotsketch
% chromatic has joined #parrotsketch
% bernhard has joined #parrotsketch
<particle> 'lo all
<mdiep> good afternoon
<chromatic> Greetings, everyone.
<chromatic> Let's get started.
<chromatic> Bernhard, are you here?
<chromatic> Okay, I'll go.
<chromatic> I fixed some bugs.
<chromatic> I'm working through the list of open patches; it's fairly small.
<chromatic> I'm going to do more work on the metamodel, to see if we can get it complete by the next release (if not the default).
<chromatic> I have notes on the FOTW, and I'll post them soon.
<chromatic> Allison's report has more details on What I Did This Weekend.
<chromatic> EOR
<chromatic> Allison?
<chromatic> - I spoke this weekend at LinuxFest Northwest (so did chromatic). I was 
<chromatic> pleased at the response, including some C hackers who were interested in 
<chromatic> contributing, and a Perl hacker who implemented a way to parallelize our 
<chromatic> test suite during chromatic's talk. We'll definitely have to speak at 
<chromatic> more Linux conferences.
<chromatic> - A good part of my Parrot time last week was taken up preparing my 
<chromatic> talk, but I've gotten pretty close to a first draft on the PMC PDD. I 
<chromatic> plan to check it in later this week.
<chromatic> Thanks, Allison.
<chromatic> Leo?
<chromatic> No Leo for now.  Matt?
<mdiep>  - Worked on [PATCH] queue; got the easy ones out of the way
<mdiep>  - Started to look at Tcl again, only to notice that chromatic's 0-length string fix broke it
<mdiep> ^D
<chromatic> Jerry?
<particle> coke's report: Implemented a basic Range class, based on S03; it's lazy, has support for most of the spec except for arithmetic and Infinities. Once someone tries to integrate into Perl6, we can clean up the interface if necessary.
<particle> my report:
<particle> ~ no commits for the past two weeks :(
<particle> ~ however, i've been busy with exporter/namespace/iterator changes, allowing export of a global with an alternate name in the destination
<particle> ~ i expect i'll have a commit soon with full spec/impl/test updates
<particle> .end
<chromatic> Steve?
<chromatic> Kevin?
<tewk> Nothing to report.  Willing to work on OO/PMC integration.
<tewk> I should have a little more time in May.
<tewk> EOR
<chromatic> Did I miss anyone?
* bernhard is back
<bernhard> Applied patches by Rob Rogers, Mark Glimes and Shawn Moore.
<bernhard> Add stub for 'Plumhead yacc'
<bernhard> .eor
<particle> pmichaud says starting tomorrow he'll have two weeks of parrot time.
<chromatic> Nifty.
<chromatic> Next question: what's blocking you?
<chromatic> Me, I could use bug admin access.
<mdiep> Unfortunately, the people who can give you those permissions don't know how to do so.
<chromatic> That means, for now, that someone with admin access could close a lot of bugs by finding all those where I've responded by applying patches.
<mdiep> I've been doing that
<mdiep> I have a saved search of all open patch tickets: http://xrl.us/vwt5
<chromatic> Nifty.
<chromatic> Are there any other blockers?
<mdiep> That string allocation bug is going to block any progress on Tcl.
<particle> i'm working on my own blockers now
<chromatic> mdiep, do you have a test case?
<chromatic> Reading the code I can't see how that would make a mess.
<chromatic> I do note that it caused FreeBSD problems, at least for 64-bit machines.
<mdiep> cd languages/tcl/; make; ../../parrot tcl.pbc t/cmd_append.t
<mdiep> I tried to come up with a smaller test case, but wasn't successful
<mdiep> I was hoping if you looked at the backtrace you'd have an idea of what was going on
<chromatic> I'll do that.
<chromatic> Anything else to discuss?
<mdiep> What happened to the File of the Week?
<chromatic> I have notes and I'll send them to the list today.
<mdiep> So realistically, it's File of the Fortnight?
<chromatic> It's file of the "I Never Get Anything Done During Conferences".
<mdiep> heh
% allison has joined #parrotsketch
<tewk> Lets pick one for this week.
<chromatic> Do you want to pick it, tewk?
<tewk> I can, but I would choose pretty arbitrarily, If there are no suggestions, I'll choose.
<chromatic> Be my guest.
<particle> can it be pdd15-related?
<particle> we still have some pdd15 impl work to do
<allison> src/objects.c?
<chromatic> Absolutely.
<tewk> Sounds good.
<tewk> I'll send out an email.
<allison> it's a hairy one
<allison> but really, even cleanups as small as typo fixes are a huge help
<allison> no fix is too small to be worth making :)
<mdiep> from the looks of it, comments explaining what each sub does would be a big help
<tewk> I'll take that one, explainations of each sub.
<particle> how about a wiki page called File of The Moment
<particle> we could describe the file, and what our goals are
<particle> or, a ticket
<chromatic> That's a decent idea.
<mdiep> I like it
<particle> we need some way to track this, in order to spread the load
<allison> sounds good
<chromatic> I like having the discussions on the list, though.  That seemed to generate further discussion with more participants than anything else we've done.
<particle> okay, ticket is better for list discussions
<tewk> I'm copying the discussion from here to the email list.
<chromatic> Speaking of files, does anyone know what the purpose of FUNDOC is and why it's not POD?
<allison> which dir?
<chromatic> src/string.c at the moment.
<particle> i have a vague recollection that there's a tools/ file to process FUNDOC
<mdiep> FUNCDOC. There's a C in the middle there.
<chromatic> Sorry, I get hung up on how FUN it is.
<allison> doesn't look like it's used very much
<allison> only in string.c in that directory
<particle> i know there's a difference in pmc vs ops comment/doc format
<particle> i guess it's unrelated, though
<particle> ...but it still bothers me
<particle> guess i should collect my thoughts and post a CAGE task
<allison> infact, the only files in the whole repository that use it are src/exec.c, src/string.c and src/gc/dod.c
<bernhard> why have we never used doxygen for documenting C-code ?
<allison> which makes me think it's a left-over from the time before we started putting POD in our c files
<chromatic> I wouldn't mind POD consistency.
<allison> make a ticket, or rip it out and see if any doc generators break
<particle> andy was working on something for c decl docs
<chromatic> Heh, Andy was also going to announce our December release.
<allison> ok, check with him first
<particle> ops2pm and pmc2pm each have their own pod-in-c-comment parsers, iirc
<particle> that's what bothers me.
<tewk> doxygen++ (POD in c files)-- too many blank lines
<allison> if either of them was doing anything with the string "FUNCDOC" it would've shown up in the grep, though
<allison> tewk: true enough, but having one consistent documentation format for all code in the repository++
<allison> tewk: blank lines are ignorable
<tewk> I'm a verticle space freak. :)
<particle> is doxygen portable enough for parrot?
<allison> tewk: you need a taller monitor ;)
<particle> i know perl 5 is....
<chromatic> Especially if there's a documentation browswer for ops someday.
<allison> anyway, chromatic could you submit a ticket about FUNCDOC? give the list a chance to comment
<allison> (the list == slow access collective memory)
<chromatic> Will do.
<chromatic> It sounds like we've wrapped up here.
<chromatic> Let's adjourn to #parrot.
% allison has left #parrotsketch
% chromatic has left #parrotsketch
% bernhard has left bernhard!~bernhard@p549A3747.dip0.t-ipconnect.de
% particle has left particle!~particle@144.81.84.216
% particle has joined #parrotsketch
% particle has left particle!~particle@144.81.84.216
% particle has joined #parrotsketch
% Steve_p has left Steve_p!~steve@pool-71-98-25-134.mdsnwi.dsl-w.verizon.net