% contingencyplan has joined #parrotsketch % rdice has joined #parrotsketch % rdice has left rdice!~richarddi@CPE001217e365c7-CM00159a01d44c.cpe.net.cable.rogers.com % rdice has joined #parrotsketch % pmichaud has joined #parrotsketch I may or may not make it to #parrotsketch today I have little to report, anyway -- other events continue to eat time :-( Sorry to hear. :-( I'm expecting it to improve (but then I always expect it to improve :-=) % cognominal has joined #parrotsketch % rgrjr has joined #parrotsketch % chromatic has joined #parrotsketch % allison has joined #parrotsketch % Coke has joined #parrotsketch hello, folks. % cotto_ has joined #parrotsketch Good day everyone. chromatic, should I arm wrestle you for it? Go ahead. Ok. patrick is out for PS today, and ISTR barney has sent his off to particle. Why don't we let particle go first with his stored reports. hiyo, pasting... barney: - Applied some patches - Added the PHPArray PMC to the standard Plumhead build. - Added the PMC tests from cotto to the standard Plumhead tests. - Got a new notebook and ran into problems with Parrot_Test.t.  kraai++ for fixing. - removed unneeded type names from PIR, RT#42769,  and caused a slight mess with error.t - Tried to beautify imcc.y .end ~ volunteered to oversee google summer of code for parrot/rakudo this year things are just starting up, i'll keep everyone up to date on the latest goings-on if you have project ideas or would like to be a mentor, please sign up http://www.perlfoundation.org/perl5/index.cgi?gsoc2008 .end % wknight8111 has joined #parrotsketch Thanks. (And thanks for volunteering for soc. =-) spinclad? or not. =-) allison? - Launched the Security PDD. Please review and comment as you have time. - Updated the PMC implementation branch from trunk, and modified new code that was added to the trunk to the PDD 17 style. - Working now on segfault report from particle for Perl 6 in PMC branch. - Otherwise, the PMC branch is ready for language testing, will plan to merge it back into trunk next weekend. EOR I believe I've fixed the .HLL problem with disappearing namespace entries and the like. I also fixed a strange memory corruption error with the clone opcode. It shouldn't leak memory either. It did, even with the destroy code in there earlier. I did some minor cleanups in a few files, but nothing big. I'm going to add one more feature to the PMC parser so that we can convert most other PMCs to use auto-generated structs. .end I did some minor updates to tcl, minor rt updates. .end cognominal ? yes? heh. Forgot who was a commiter and who wasn't. I need a list. Oh wait, I have one. I need to *read* the list. =-) I am not a commiter and I have a patch pending We'll make sure it gets reviewed. rgrjr? * tweaked some internal tools (pdump, pbc_header.pl). * read up on memory management. still only slightly better clued. * chromatic's progress on GC bugs has helped Kea-CL greatly. on the other hand, i'm still getting similar problems, which are larger and therefore harder to file reports on. .eor tene ? Absolutely nothing! Detroit was far more distracting than I anticipated. I don't know anyone in Phoenix, so I'm hopeful about this week. .eor heh. tewk? I think that's all the committers that are about; anyone else have a report that I missed, any questions to queue up? I have a question for allison. Oh, I have an item I forgot to mention. (which I can phrase as a question) go ahead. =-) I set up http://www.parrotblog.org this week, for parrot developers. Would anyone like an account? If so, email me your gmail account (create one if you don't have one). Can I ha... oh, right. =-) How would you expect this to work with developers individual blogs, things aggregated in parrot, etc? Okay, back to questions. and, that's a question... er, in planet parrot. I'm not doing aggregating, because I don't want to pull in developer's non-parrot posts but, double-posting is fine Should I add it to planet parrot? it'll even let you email in your posts yah, that'd be good Ok. Taken as a todo. I've requested commit access for working on plumhead. How soon should I expect to hear back about that? whoops. I hadn't gotten past the email you sent on that. But everyone I would have mentioned it to is here. Give us a day to chew on it. no problem allison: we had talked just before 0.5.3 about rolling back pdd17 into trunk; do you have an ETA on that? I know we wanted to ping HLL developers to check it out before you pulled the trigger... If we can fix particle's segfault, she should be able to merge it very soon. I just asked for HLL testing in my report today, I'll also mention it on the list if all goes well, plan to merge it in on Saturday fab i'll be around this week for testing hlls particle: excellent! (all goes well) fair enough. Anyone else have a question? I'm thinking of submitting a YAPC::NA talk proposal about how to use continuations etc. to do fancy control structures, but am worried that this is the wrong audience and/or old hat. WDYT? rgrjr: sounds like a great idea I would attend that talk. Does that help? it's a useful concept in any language rgrjr: If I were attending YAPC::NA, I'd attend such a talk. I'll be at YAPC::NA, btw. Great; thanks for your support. There is the ticklish issue of whether PCT supports what I am doing without it . . . I must say that we have a french perl workshop in France at the end of may 30 and 31 if I recall, everyone is welcome to come to talk about anything Perl 6/Parrot rgrjr: Just because the ivory tower of #ps thinks it's old hat doesn't mean that there's not a whole bunch of parroteers or perl6ers that wouldn't benefit from it :) I'm scheduled for an intro-level presentation on Parrot at Penguicon, in Detroit in April. tene: great! cognominal: not i; i'm taking too much time of this summer as it is. Anyone else have anything report-y or question-y ? Are we on track for the next release? if anyone could spare some tuits, we could have a yaml dumper for past quite easily seems to me we're on track for a 0.6 if we get pdd17pmc merged I'd be happy to call the next release 0.6 then, ya. ah... will pdd17pmc have any affect on freeze/thaw code? It shouldn't. fab. chromatic: I think the biggest thing for next release is the merge. particle: yeah, we're keeping the structures the same, just generating them (yaml dumper): and a developer or two eagerly awaiting! the yaml dumper is very, very close to working. just needs a few pir tuits to finish it off particle: I have some PIR tuits, as I'm going blind looking at tcl. Ping me after meeting. hokay! I'll ping barney to make sure he's on track for the release, also. Anything else? isn't it traditional to ask about fun and blocking? :) blocking is rarely fun. I was waiting to make sure there were no more questions. =-) "what perljam said" ? definitely having fun excellent. I have more fun after I've fixed strange bugs than during the process of fixing them. If someone's not having fun, of course feel free to ping me privately if you don't want to drag it out here. chromatic: I'll try to find more strange bugs you can fix to make you happy, then. b i'm swamped. no fun, that. Sadly, I can't manufacture tuits. i feel like the u.s. dollar lately. alright. I think that's a wrap. * particle hopes pdd17pmc will finally allow me to subclass Exporter PMC in pir we'll get into that next week, after merge cya particle: it will, with a few updates to PMCProxy \o/ Ok. now I hesitate to say it's a wrap again. =-) really, it's a wrap :) On the off chance it is, have a great week, see you all next tuesday if not before. ^_^ % allison has left #parrotsketch % chromatic has left #parrotsketch % wknight8111 has left #parrotsketch % cotto_ has left #parrotsketch % rgrjr has left #parrotsketch % Coke has left #parrotsketch % rdice has left rdice!~richard_d@CPE0014bfafbbd5-CM0011e6ecf48a.cpe.net.cable.rogers.com % rdice has joined #parrotsketch % rdice has left rdice!~richard_d@CPE0014bfafbbd5-CM0011e6ecf48a.cpe.net.cable.rogers.com % rdice has joined #parrotsketch % rdice has left rdice!~richard_d@CPE0014bfafbbd5-CM0011e6ecf48a.cpe.net.cable.rogers.com % particle has left particle!~particle@c-24-19-3-148.hsd1.mn.comcast.net % particle has joined #parrotsketch % contingencyplan has left contingencyplan!~contingen@cpe-76-186-27-146.tx.res.rr.com % contingencyplan has joined #parrotsketch