% particle has joined #parrotsketch
% coke has joined #parrotsketch
% coke has left #parrotsketch
% avar has left avar!~avar@dsl-228-236.hive.is
% rafl has left rafl!~rafl@armitage.dreker.org
% avar has joined #parrotsketch
% smash has joined #parrotsketch
% PerlJam has left PerlJam!duff@feather.perl6.nl
% leo_ has left leo_!lt@feather.perl6.nl
% particle has left particle!~particle@144.81.84.140
% mugwump has left mugwump!~samv@watts.utsl.gen.nz
% particle has joined #parrotsketch
% PerlJam has joined #parrotsketch
% mugwump has joined #parrotsketch
% leo_ has joined #parrotsketch
% allison has joined #parrotsketch
<particle> hi ho, all
% chromatic has joined #parrotsketch
<particle> obra's not around this week due to travel schedule changes
<particle> who's here this week?
<chromatic> You are.
<particle> am not!
% davidfetter has joined #parrotsketch
<particle> well, this promises to be a short meeting. let's wait a few more minutes for stragglers
<allison> I'm here
<particle> oh, patrick won't be around today, either, but the release is scheduled for tomorrow.
% bernhard has joined #parrotsketch
% jisom has joined #parrotsketch
<particle> ok, let's get started. chromatic, what's new?
<chromatic> I fixed several little bugs and have all tests passing on x86 and PPC Linux.
<chromatic> I also mostly have a Makefile working for Parrot::Embed.
<chromatic> I may or may not have a Pure-PIR PBC to C Bundle working.
<chromatic> I see that there are some regressions in Pheme, so I'll try to fix those today.
<chromatic> EOF
<particle> allison?
<allison> - At chromatic's request, I refactored HLLCompiler so you can configure the OST compilation process to use a different module, and so you can add and remove stages in the compilation process.
<allison> - We had a great bug squashing session on Saturday. (With the time zone difference I was wrapping up for the evening just as others were getting started.)
<allison> - I'm also still mulling over objects PDD.
<allison> EOR
<particle> ~ approved kid51++ ops2pm tests and refactor to merge to trunk
<particle> ~ helping chromatic++ with Parrot::Embed windows porting
<particle> ~ fixing some failing distro tests
<particle> ~ doing release prep work to help pmichaud++ (NEWS, CREDITS, etc.)
<particle> ~ still having trouble with parrot metacommitter interface, but i'm working on it and will document the procedure once it works
<particle> .end
<particle> ok, that's all the reports i have for this week. the big news is tomorrow's release. any blockers?
<chromatic> Seems okay here.
<particle> seems like no. none for me, either. it looks like this one will go smoothly.
<mugwump> any thoughts on the optimisation defaults?
<particle> btw, any language authors reading this, please update NEWS with a news item if your language has progressed this month
<chromatic> I thought the reason we use the slow core by default was because the fast ones don't compile or work on all platforms.
<chromatic> That thought is a couple of years old though.
<particle> slow core is most portable, for sure
<particle> patrick's not here today to say for sure, but if it were up to me, we wouldn't turn on optimizations for this release
<particle> we haven't tested it well enough
<particle> we don't have any smoke reports with optimized non-debug builds
<jisom> just skip this release and work on it for next release?
<chromatic> Agreed.
<particle> however, correct and complete always trumps optimized. unless there's a pie in the face at stake
<particle> so, feel free to work on it, but it's not a milestone item.
<mugwump> has anyone looked at the bug in the addparent opcode?
<chromatic> We should probably fix any optimization problems on the target platforms anyway, so getting wider testing will help.
<particle> i'm more interested in porting than optimizations
<smash> vmserver is up&running, currently hosted systems are debian and windows xp.. 
<allison> mugwump: did you submit is as a separate bug report? or just the patch with the failing test?
<allison> mugwump: I was looking for it on Saturday, but didn't find it
<particle> hang on here, a moment, folks.
<particle> this is a moderated meeting. if you're not a regular reporter, please speak only when spoken to.
<particle> (as a rule).
<particle> this week, things are quiet, and question time has begun, so let's open the floor for questions.
<particle> first, let's address mugwump's.
<mugwump> particle: my apologies, I spent last week watching and thought it would be ok
% smash has left #parrotsketch
<particle> no problem, go on.
<mugwump> ok, so, anyway, the implementation for subclass and addparent seem to be independent, and the "addparent" one doesn't work completely
<mugwump> I think the mro list is built wrong
<chromatic> Can you make some tests for that?
<mugwump> allison already committed one I submitted
<allison> they're TODO tests
<chromatic> Fantastic.
<allison> t/pmc/object-meths.t
<mugwump> http://utsl.gen.nz/gitweb/?p=parrot;a=commitdiff;h=95382353 is the commit
<allison> mugwump: could you submit a description of the bug to the ticket queue with a prefix of [BUG]?
<allison> and reference the TODO test
<mugwump> ok, will do
<allison> that'll make sure we catch it before the next release
<chromatic> Next question: Alek Storm's patch.  It looks good to me, but is it too close to the release?
<allison> c: let's wait 2 days
<chromatic> Okay.
<allison> "potential unintended side effects"
<chromatic> I'm okay with avoiding C code patches for a day or so before release.
<particle> yeah, let's concentrate on failing tests and documentation updates until release
<chromatic> Are there still failing tests?
<particle> yes, in t/distro
<particle> i'm working on them, so is ptc, who should be doing a metadata update later today
<jisom> what about #41538?  if someone knows the io internals well enough it might be easy to fix, and not something to put into a test
<chromatic> jisom, I saw that.  I may be able to fix that shortly.
<jisom> alright
<allison> is tewk here?
<chromatic> Segfaults for me too.
<particle> looks like tewk isn't around.
<allison> yup, I'll email (he has a draft port of SMOP)
<jisom> yeah, I think it just tries to keep reading data until it finds a newline, but if it's going into parrot's other data, it's fairly random about if it really screws up and seg faults but does most of the time
<particle> allison, you mentioned something (saturday?) about parrot calling conventions and c
<allison> more context?
<particle> tewk implemented pcc in c
<allison> yes
<particle> i thought you didn't know about that
<particle> just making sure you did.
<allison> we talked about it on Saturday
<particle> great, i must have missed taht.
<allison> ok, cool
<allison> has he checked it in yet?
<particle> yes!
<particle> t/pmc/pmethod_test.t
<allison> cool, I'll try it out
<allison> tewk++
<particle> anything else for this week?
<allison> I guess not
<particle> ok then. see you next week!
<obra> hey all
<chromatic> Pfft, that was so 1:21 ago Jesse.
<obra> Yeah, well.
<obra> AA cancelled my flight
<obra> so I started an hour earlier, get home an hour later and have less time on the ground to charge my laptop half way through
<obra> :/
<chromatic> The important thing is that they still inconvenienced you.
<obra> ...I've now flown about 30,000 miles in 5 weeks.
<obra> I've had all my inconivenience
<chromatic> Are you blocking on anything?
<obra> Power, network and enough time in one city to think
<obra> I've been talking to ovid, bill and dave about possible new grant opportunties to help get folks excited about parrot and other perl 6 hacking
<allison> new source of funding?
<chromatic> Panhandling.
<allison> heh :)
% bernhard has left bernhard!~bernhard@p549A2679.dip0.t-ipconnect.de
* PerlJam just wishes we could win over some of the naysayers.
<allison> nothing speaks louder than working code
<PerlJam> Not that it's a model to follow, but certain other languages have done quite well on mostly hype :)
<chromatic> We need a shiny-faced Dutch man.
<allison> ah, but it's hype plus working code
<allison> the code may not be as shiny as advertized
<chromatic> Someday I should show you all my failed RoR project.
<allison> but it doesn't shatter the illusions too hard
<allison> c: Danish?
<chromatic> No thanks, I just had toast.
* particle would like a danish
<allison> a nice crispy piece of toast?
<allison> perhaps a bagel?
<allison> er, when the Red Dwarf scripts start coming out, it's time to wrap :)
<allison> I've got to go find dinner
<allison> catch ya' next week
<PerlJam> embedding parrot in apache and in browsers would be tres cool IMHO
<allison> yes, it's definitely a plot we're working toward
% allison has left #parrotsketch
<chromatic> Parrot Vindaloo?
<PerlJam> it would certianly put php's ubiquity to shame :)
<jisom> take out java and php, and perl5 of course
<mugwump> a parrot browser plug-in could work for browsers that won't move to a parrot based JS interpreter :)
<obra> (In this case, the funding is based on unallocated $ that got donated a few years ago)
% jisom has left jisom!~jisom@74-134-230-123.dhcp.insightbb.com
<avar> a1
% chromatic has left chromatic!~chromatic@sub17-30.member.dsl-only.net
% chromatic has joined #parrotsketch
% chromatic has left chromatic!~chromatic@63.105.17.30
% chromatic has joined #parrotsketch
% chromatic has left #parrotsketch
% davidfetter has left davidfetter!~davidfett@start.fetter.org
% particle has left particle!~particle@144.81.84.140
% particle has joined #parrotsketch
% avar has left avar!~avar@dsl-228-236.hive.is
% avar has joined #parrotsketch