% pmichaud has joined #parrotsketch
% Coke has left #parrotsketch
% integral has left integral!bsmith@adsl-212-20-244-147.lumison.co.uk
% integral has joined #parrotsketch
% chromatic has joined #parrotsketch
% PerlJam has joined #parrotsketch
% bernhard has joined #parrotsketch
% particle has joined #parrotsketch
<chromatic> Good news, everyone.
<pmichaud> what's the good news?
<chromatic> I dunno, it's just what Prof. Farnsworth always said on Futurama.
<pmichaud> That is good news!
% rdice has joined #parrotsketch
% jisom has joined #parrotsketch
% davidfetter has joined #parrotsketch
<chromatic> Shall we begin?
<chromatic> I have Allison's report.
<chromatic> I've primarily been working on the PMC PDD. It's mostly there, but still has a few high-level decisions left to be made. It won't be a radical change. (I nearly rejected variable-sized PMCs as not worth delaying the 1.0 release, but some of the features are necessary to support inheritance between low-level PMCs and high-level classes.
<chromatic> I've also been working on a patch to update the Class PMC to register a type number.
<chromatic> I'm on my way to the airport, but will be around to answer questions in the later part of #parrotsketch.
<chromatic> That was Allison.
<chromatic> bernhard?
<bernhard> Apply patches by Psyche, Kiwi and Mehmet.
<bernhard> Remove opcodes  adddoes, removedoes and singleton.
<bernhard> Try to fix Tetris, unsuccessfully.
<bernhard> Prevent coredumps from option --pre-process-only.
<bernhard> Add two macro tests.
<bernhard> Fiddle with languages/lisp.
<bernhard> Correspond with Roger Conley about a Parrot Firefox plugin.
<bernhard> .eor
<chromatic> I fixed some bugs.
<chromatic> I cleaned some code.
<chromatic> I have some comments about our finalization/destruction strategy and some questions about memory allocation/deallocation in src/debug.c.
<chromatic> I also found a way to make GCC hide non-exported symbols in shared libraries, which ought to help us reclaim some tests skipped on Windows.
<chromatic> Then I ran into a question about invoking non-Sub sub PMCs from C, not within Parrot.
<chromatic> EOR
<chromatic> leo, are you here?
<chromatic> particle, hang up and type.  Or we can come back to you.
<particle> no real parrot commits this week. recent mailing list activity has kept me thinking, but haven't gotten around to acting yet. fiddling with ack.
<particle> .end
<chromatic> pmichaud?
<pmichaud> * Spent Thu-Sun at a (non-perl-related) workshop
<pmichaud> ** I did wear my perl shirt, however, and got lots of enthusiastic
<pmichaud>    questions about the status of Parrot and Perl 6
<pmichaud> ** Many people thought that the Perl "onion" logo was actually garlic.
<pmichaud> * The non-PIR parse tree transformation language is continuing to
<pmichaud>   inch closer to realization
<pmichaud> * I had hoped to have code ready by today's #parrotsketch, but I
<pmichaud>   still need to get the transformations for bottom-up parsing
<pmichaud>   a little more fleshed out.
<pmichaud> * Still, I'm very excited by this approach, and expect to be
<pmichaud>   pushing commits to svn tonight or tomorrow.
<pmichaud> * I need a name for the new language.  I might use "onion".
<pmichaud> * Or maybe I'll just call it "garlic".  :-)
<pmichaud> * I have designs in place for implementing (in PIR)
<pmichaud>   contextual variables, which will be _very_ useful for PGE,
<pmichaud>   PAST-pm, and a number of our other tools that make heavy
<pmichaud>   use of context.
<pmichaud> * This morning I sent a longish message to parrot-porters
<pmichaud>   outlining my experience with implementing assignment
<pmichaud>   operations on PMCs in PIR  -- looking for feedback on that
<pmichaud> .end
<chromatic> pnion (pronounced pun-yun)
<chromatic> tewk?
<chromatic> Anyone else I skipped or who came in late?
<pmichaud> "pennie"  (to go along with ponie, punie, and pynie)
<davidfetter> paglio
<pmichaud> or, for pasta lovers, "penne"
<bernhard> pygmy
<chromatic> pagliacci
<pmichaud> or maybe even "vinnie", since "vi" is the roman numeral for "6"  :-)
<pmichaud> "My Language Vinnie"
* davidfetter queues up the theme from the godfather
<particle> vidalia
<chromatic> emacsinni
* pmichaud apologies.
* pmichaud apologizes.
<chromatic> Alrighty, are there any questions we should discuss now?
<jisom> re: documentation, jit
<chromatic> Go ahead.
<jisom> well the documentation in src/jit/ isn't as great as it could be, we don't have a sample core.jit file to clearly explain it all, and the skeleton/jit_emit.h file doesn't fully reflect the current state of things afaict(I'm using it for my amd64 jit)....the files for creating an executable file aren't explained well either......
<chromatic> In my experience, the best way to fix this is to ask Leo lots of questions and expand his answers into fuller documentation.
<chromatic> Another option is to take one of the JIT files as a FOTW and see if we can get more comments on that by having people read it.
<chromatic> I suspect the first option will help the second though.
<jisom> he's removed himself out of RESPONSIBLE_PARTIES, but I've been poking and prodding around the source, and figuring stuff out.........so I imagine some of the documentation will fall on me if I can get my amd64 jit working
<chromatic> Leo's still pretty good about answering questions directly.
<pmichaud> I suspect he would still eagerly answer questions about jit
<jisom> yeah
<jisom> for the moment, I've skipped porting the i386 to amd64 and I'm going off of the skeleton jit
<chromatic> More power to anyone who writes any part of the documentation, even just an outline on what's there and how it fits together.
<jisom> true
<particle> on another topic, it seems our pm isn't available for these meetings. although he's often on irc and available by email, i'd like to see if we can get a better time for this meeting so the project team can attend regularly.
<particle> any objections to the possibility of a #parrotsketch time shift?
<pmichaud> no objection
<chromatic> I'm open to the idea.
<pmichaud> I'm generally unavailable 16:00-17:30 UTC
<particle> i'll let coke know
<pmichaud> (on tuesdays -- other days have different constraints)
<chromatic> Meanwhile, tewk has a report.
<chromatic> tewk?
<tewk> Report:
<tewk> I'm almost done with a complete revamp of Pmc2c.
<tewk> Only the special case pmc generation to finish up such as delegate, deleg_pmc, shared, stm, etc.
<tewk> This should make it much easier to implement upcoming PMC changes.
<tewk> I promised to get this into a branch, which I commit on doing this pm.
<tewk> EOR
<chromatic> Lovely.
<particle> indeed
<particle> oh, i'll be off on vacation for a week starting tomorrow
<particle> so i'll miss next week's meeting
<chromatic> I'll do your report for you.
<chromatic> "On vacation.  HA ha."
<chromatic> Anything else?
<chromatic> Has everyone been reading the commit logs?
<pmichaud> sporadically
<chromatic> Well in the absence of any other discussion, let's adjourn to #parrot and to next week.
<pmichaud> okay
<jisom> my tcsh alias, alias svnup   set oldrevision = `svn info | grep "Last Changed Rev" | cut -d " " -f 4`; @ oldrevision++; svn up; set newrevision = `svn info | grep "Last Changed Rev" | cut -d " " -f 4`; if ($newrevision != "") if ($newrevision >= $oldrevision) svn log -r ${oldrevision}:${newrevision};
<jisom> use it, share it, bsd it! :-p
% particle has left #parrotsketch
% davidfetter has left #parrotsketch
% chromatic has left #parrotsketch
% allison has joined #parrotsketch
% allison has left allison!~chatzilla@ip67-88-206-99.z206-88-67.customer.algx.net
% jisom has left jisom!~jisom@74-134-230-123.dhcp.insightbb.com
% rdice has left rdice!~rdice@CPE0014bfafbbd5-CM0011e6ecf48a.cpe.net.cable.rogers.com
% bernhard has left bernhard!~bernhard@p549A1F08.dip0.t-ipconnect.de
% pmichaud has left #parrotsketch
% integral has left integral!bsmith@adsl-212-20-244-147.lumison.co.uk
% integral has joined #parrotsketch
% integral has left integral!bsmith@adsl-212-20-244-147.lumison.co.uk
% integral has joined #parrotsketch