% rdice has joined #parrotsketch % pmichaud has joined #parrotsketch % kid51 has joined #parrotsketch % jonathan has joined #parrotsketch % particl1 has joined #parrotsketch % particle has left particle!~particle@c-24-19-3-148.hsd1.mn.comcast.net % smash has joined #parrotsketch * smash hello everyone Howdy, smash, you fine fellow! * kid51 had to say it 'cause purl's not here. % barney has joined #parrotsketch % allison has joined #parrotsketch okay, no Coke or chromatic here today let's see... barney, jonathan? yep anything to report? hacked on Eclectus .eor jonathan mentioned he was on his way out the door particle, pmichaud? I haven't seen particle this morning, so I'll go ahead and report parrot: * updated pbc_to_exe to eliminate compiler warnings, speed improvements * allow pbc_to_exe and the files it creates to run from any directory * pbc_to_exe is still tied to the build directory, though -- fixing this will require cleaning up parrot's "make install" pct: * fixed the --target=pir option for interactive mode nqp: * applied fixes from Tene for hashes and arrays perl6: * watched others (particle, jonathan, coke, etc.) add new features to perl6 * refactored documentation, updated README, submission guidelines, STATUS * added docs/compiler_overview.pod ** I'm hoping compiler_overview.pod can be a start for writing generic compiler tools documentation * added 'module' keyword and namespaces * refactored infix:<~~> (smart matching) * added infix: (defined-or) * wrote some Perl 6 articles for perlbuzz, journal posts * added a 'make perl6' target to generate a standalone executable with pbc_to_ex e * added @*ARGS support, so hanoi.pl now runs * refactored some RT tickets * created a metaticket for high-priority perl6 items * eager to see Coke's spiffy new online RT summarizer plan: * initiate official test suite refactoring and review * write two articles about adding features to perl6 * update PCT and perl6 to use 'copy' opcode * update perl6 ROADMAP blockers: * fglock is blocking on dynamic :outer (RT#49182) * many new hackers and compiler users will probably need RT#43269, or a workarou nd EOR busy couple of weeks! :) jonathan? (he mentioned he was still here) * Gave a lightning talk about implementing Perl 6 given statement, then checked it in at the end of the talk, at the Israeli Perl Workshop. * Started digging into the junctions implementation. Much left to do, but also quite a bit done. * Other little tiny things in languages/perl6/ * Auto-threading of junctions on sub calls is next up. * Not much Parrot core work, but I will try and get back into that soonish. EOR smash? tewk? no report soz, bu i have a question kid51? Yes several points A lot of refactoring of the configuration system which, if done correctly, should mostly be invisible to other Parrot developers. Most prominently, revised the subs used by config/auto/*.pm to build and run little C programs which probe the OS for config values -- such as cc_build, cc_run -- now are methods in Parrot::Configure::Compiler and must be invoked as, e.g., $conf->cc_build(). These methods are inherited by Parrot::Configure object. So now, when these methods are invoked they have access to all data stored in Parrot::Configure object at time of invocation. In many config step classes, I've refactored the guts of runstep() out into internal methods/subroutines and have written tests directly for them in t/configure/1??-*.t. This boosts the test coverage considerably (see http://thenceforward.net/parrot/coverage/configure-build/coverage.html). Coke showed me how to search for all tickets which I've taken (as distinct from those I opened). This has enable me to go through several old tickets and resolve them. There's a guy who works in NYC (and who is not named Dan!) who is showing interest in the project. I'm hoping to be able to achieve F2F hacking with him. Next week will be attending a BSD users meeting. Would like to recruit smoke testers for BSDs besides FreeBSD and Dragonfly. Cf.: http://rt.perl.org/rt3/Ticket/Display.html?id=49276. EOR allison? - Spent the past 2 weeks removing the tendrils of the old event system so I could turn it off. Timers, sleep, NCI callbacks, and thread suspension for GC now on new concurrency scheduler. - Ended up solving some mod_parrot thread-related crashes in the process, which was a nice side-effect. - Checked in changes with a few intermittently failing tests to get broader platform testing and review. Thanks to all for your reports. - Currently working on implementing one more significant piece of PDD 25, which should resolve the remaining failing tests. - Updated the debian packaging metadata in the repository. - Wrote a debian packaging guide. - Wrote a guide to setting up a chroot environment for testing and generating packages in various versions of Debian and Ubuntu. EOR any other reports before questions? minireport * fixed the scheduler.c breakage and made it compile on Win32 with Jonathan * will try to find some time slots and round tuits for parrot dev in 2008 leo++ (welcome back) thx leo++ questions, smash you had one? yes, anything o i can do to help that debian package thing ? read through the chroot instructions and packaging guide and try them out that will help catch any steps I didn't document ok I'd like it to be as repeatable as possible (similar to our standard release guide) * smash nods other questions? re: Our smoke test reporting system It's < optimal, IMHO. I'd like to be able to search it by tester, by individual test, etc. the submission process, or the interface to review them? Who, if anyone, is "in charge" of it? Can we recruit someone to overhaul it? allison: Main concern is interface and what's behind it -- but, then again, my own smoke was submitted and not displayed. I'd like to get more info out of it a la cpan.testers certainly we can recruit someone for improvements someone was working on it at YAPC::EU, but haven't heard from them since then I assume it's hosted at perl.org -- but where is the code housed? (hosted at perl.org) yes wasn't that tools/util in the Parrot repo? smokeserv-server.pl barney++ there's even a README :-) * barney suggests a tools/smoke dir barney: agreed are there enough items to warrant a separate smoke/ dir? (I'm not opposed, just asking) is the smokeserv-server.pl on a machine, where folks can change that file? I suspect it's wherever the other parrotcode.org files are kid51: are you offering to find a volunteer? pmichaud: those are in the perl.org combust repository, all flat templated html allison: I think that, after studying what's in tools/util/, I'd like to start a wiki page that would be an evolving spec for a better smoke server kid51: sounds good I think that wraps up that one. other questions? Okay, back to coding. Happy New Year everyone! happy 2008, all -""- % pmichaud has left #parrotsketch * kid51 nods at #parrotsketch and gives him a small kipper a guats neis % kid51 has left #parrotsketch % chromatic has joined #parrotsketch % barney has left barney!~bernhard@p549A0B8E.dip0.t-ipconnect.de % chromatic has left #parrotsketch % allison has left #parrotsketch % jonathan has left #parrotsketch % rdice has left rdice!~richarddi@CPE001217e365c7-CM00159a01d44c.cpe.net.cable.rogers.com % rdice has joined #parrotsketch % rdice has left rdice!~richarddi@CPE001217e365c7-CM00159a01d44c.cpe.net.cable.rogers.com % particl1 is now known as particle