% cognominal has left cognominal!~stef@cac94-1-82-67-232-89.fbx.proxad.net % cognominal has joined #parrotsketch % cognominal has left cognominal!~stef@cac94-1-82-67-232-89.fbx.proxad.net % cognominal has joined #parrotsketch % cognominal has left cognominal!~stef@cac94-1-82-67-232-89.fbx.proxad.net % cognominal has joined #parrotsketch % leo has joined #parrotsketch % mdiep has joined #parrotsketch 'afternoon Parrot Sketch Roll Call. Who's around? hi all helol % pmichaud has joined #parrotsketch err, hello hello right then. let's get rolling. What's new, Patrick? or, say, leo % particle has joined #parrotsketch - Released Parrot 0.4.0 "Luthor" - moved return value passing out of *Continuation.invoke into the set_returns opcode and created a PIC (polymorphic inline cache) version of it - speeds up the fib benchmark by 25% - it's also the base for not creating a plain return continuation at all, just for returning from a sub, but that's optimization aka later - not much else last week, code cleanup, bug fixes and such ^Z Blocking on anything? no, still a lot todo More important question: Are you having fun? a spec for named argument passing would be fun though I have always fun hacking Parrot ;-) Cool. mdiep: what's up? sorry to interrupt, but I can only stay for a second -- I'm at home with sick kiddies ok. then go for it, patrick. if you have time to report, great. little to report from my end (for reason just cited), glad to see the 0.4 parrot release I hope the kids feel better. Flu? kids should be back in school tomorrow. Yes, probably flue flu I'm still doing parsing stuff and will work on the 800 p5regex tests heh. I'll also see about recruiting people to help with the regex tests :-) nice I hope to get more people hacking on the pge guts % chromatic has joined #parrotsketch anyway, I have to go prepare lunch not blocking on anything except time at the moment. It would be nice to have a named argument spec. :-) Having fun? oh yes, definitely :) that's my report, and I'm afk for a while cool. enjoy the lunch and the feeding juice to the little ones popping back. matt: what's new? it was a slower week for tcl as well some minor code cleanup % Coke has joined #parrotsketch coke improved the compiler status this week -- we can now autogenerate builtin subs from the inline'd versions Klaas-Jan Stol was kind enough to do a little hacking and provided a [flush] implementation for us coke also added dummy version of some builtins that we're missing so that we can start working on being able to run tcl's test suite natively very cool. Let me guess. You guys want a named args spec sounds like a good guess ;-) after a little complaining on #parrot, leo implemented errors for PIR sub parameter under/overflow, which is helpful. but we're still waiting to be able to use .param with it. we will eventually need a named args spec, yes :-) I don't know that it's high on our priority list though Ok :) and also, the namespace spec hit the list this week there's a fair amount of discussion. I'm still trying to catch up with all of it. ^D having fun? the namespace spec isn't the most fun for me. but I got to hack on partcl itself some this week, and that's fun. mdiep: sorry ;-) I'm hoping that my part in the namespace design is almost over (In case anyone can't tell, I've recently been reminded about _why_ people contribute to opensource development. And what project management can do for them. And if we're not actually optimizing for fun, there are problems) heh. obra++ mdiep: blocking on anything else? nope. just the ability to use .param inside of exception handlers. I mostly see my role as: making sure that the developers are getting what they need, enjoying themselves and actually communicating amongst themselves and with the community. (In no particular order. All are important) Are there other things I should be doing that I'm not? mdiep: you are writing a compiler - just emitting 'get_results' can't be a problem (Consider this my report ;) leo: not necessarily a problem, just more work. it's one macro (last time I looked) mdiep: and of course patches welcome ;-) ok. next report, I suppose. chip: you here? or autrijus or chromatic I'm here. I checked in the basic Test::More, sans tests. I can add the like() and unlike() shortly, but for the sake of maintainability I plan to macroize most of the MMD variants, as they're all very similar except for coercions. I have two sticking points. First, load_bytecode only runs once. That is, if you try it on the same file more than once, from two different places, you get an error about not being able to run initialization code. Patrick has run into this too. Second, I don't have a good place yet to stick the tests for modules. Perl 5 uses the ext/ directory to store modules, but it's a terrible name and it doesn't have to run tests with two different programs (Parrot and Perl). I think the right solution is to create a t/modules directory and make sure that all tests run through a little harness file there. I haven't looked at the test target in the Makefile though, so it may be even easier than that. anything else? chromatic: having fun? I wish Parrot ran on my DS. That would be Very Fun. Nintendo DS? That's right. What does the devkit look like? I haven't looked yet; I doubt there's one available to non-publishers such as you and I. % allison has joined #parrotsketch ok. aside from your sticking points, do you have blockers? The library loading is going to block me very soon. chromatic: http://www.metrowerks.com/MW/Develop/Games/Nintendo_DS.htm The other won't. It sounds like Jerry Gay has a solution. cool. chromatic: the lib loading stuff is very high in priority of fixes for next release I'm happy to write a test for it if that would help double loading prevention and such - would be great to have tests ok. anything else before I turn to allison? Allison: what's new and exciting? I pushed Punie to the point where it's emitting PIR and compiling it the whole PAST->POST->PIR phase went much faster than I expected. That encourages me that the design is heading in the right direction. Next is to build up more and more complex syntax in Punie. starting with "print 'ok 1'" nice. got a failing test yet? Well, all the language tests were failing for the past month. :) :P Still have several TODOs that Autrijus checked in. Whatcha blocking on? nothing at the moment have a Q for later EOR Having fun? yes! :) woot! chip, autrijus: Last Chance! obra: I've got one more blocking item for Tcl mdiep: what is it? coke reminded me that we have a weird segfault (#37814) when trying to run the tcltest harness natively http://rt.perl.org/rt3/Ticket/Display.html?id=37814 mdiep: that's the lib loading stuff leo: ah, excellent. we'll be looking forward to the fix. :-) leo: perhaps you can add a note to the ticket stating such? ok. question time. who has questions? (and for sure a reason that I don't even look at .param for exception handlers, it there is a working solution ;-) mdiep: will do question: what will the process look like for creating a PDD from the namespace spec? I suspect that it's a question for chip looks like, yes my Q was the obj.method() syntax well, as answered in the mail, it's sometimes useful, it's ambiguous, and we might need a better syntax for the variable case e.g. like the proposed obj.$method() OTOH obj."method"() is always ok * allison searching p6i mailbox for reply mmmm... ok $ works but obj.$$P1() is a little confusing then we sould forbid the bare word? I like the bare word there is already a $ - we special case that one probably it's just the multiple meanings that cause problems hmm that's with all the bare words in imcc sytax If I were to choose one meaning for the bareword it would be "call the method with this name on this obj" sure, but in your case you additionally have .local pmc method now what then the bare word is a declared variable and it is correct sill, but doesn't DWIM for you I suspect it's a bigger problem than just method calls it is for sure not a "today" solution I fear not - no Ok. anything else for today? Right. It was pointed out to me that I hadn't said "hello" to our listening audience in a while. So, hello, lurkers. We've got a few ground rules here Conveniently, everybody's been honoring em ;) So. the deal is: * ParrotSketch is a weekly meeting. * It's open to the public - for listening only * It's publically archived * If you aren't an invited participant (IE, the moderator has asked you to join and report), you should keep quiet, though feel free to message the moderator privately. * Right now, we don't enforce any of that technically and as long as the rest of the audience stays as polite as you all do, we never will. So, thanks! And I hope it's interesting and useful. See y'all next week, gang. see ya and thanks obra (And yes, I'm usually the moderator, though occasionally, I ask someone else to fill in for me) thanks, obra % allison has left allison!~allison@sub17-30.member.dsl-only.net % chromatic has left #parrotsketch % Coke has left #parrotsketch % pmichaud has left pmichaud!~chatzilla@c-24-1-26-255.hsd1.tx.comcast.net % particle_ has joined #parrotsketch % particle has left particle!~particle@144.81.84.172 % particle_ is now known as particle