|
Post closed tickets in your report. | Note: This channel is for our weekly status meetings (Tuesdays at 19:30 UTC); you probably want #parrot instead. | irclog: irclog.perlgeek.de/ Set by moderator on 20 October 2013. |
|||
|
13:30
lizmat joined
14:43
bluescreen joined
16:35
Coke joined,
Util joined
16:40
pmichaud joined
19:09
lizmat joined
|
|||
| Util | Pre-report: | 19:29 | |
| # Done: | |||
| * Merged branch 'new-packfile-api'. Much thanks to rurban++ and gerdr++ | |||
| * Caught up with filing 10 new issue tickets from Zefram++ | |||
| * Flagged all the old Zefram tickets with the Component and Priority|Severity that he had supplied, but I had omitted. | |||
| * Fixed typos in Perl 6 specs. | |||
| * Upgraded from OS X Mountain Lion to Mavericks | |||
| + To allow me to work on github.com/parrot/parrot/issues/1016 | |||
| # Plan to do: | |||
| * GH#1016 | |||
| .end | |||
| Hello! Who all is in attendence? | 19:30 | ||
|
19:32
rurban1 joined
|
|||
| Util | No worries; we usually have such attendance issues just after the time changes. | 19:32 | |
| rurban | I got nothing to report. But we got some sev-high bugs now | 19:37 | |
| Util | True. I am tackling GH#1016 due to it bugging me, but we should start talking about severity and priority, and actually work from those. | 19:39 | |
| rurban | no blocker, 1 new critical, 4 old critical | ||
| Util | That is not to say that Zefram's assessment of severity and priority has to become *our* assessment, but it is a very good starting place. | 19:40 | |
| rurban | benabik++ for doing the actual work on the new-packfile-api | 19:42 | |
| Util | GH#548 is marked critical, and since I need to revisit the Complex class anyway, I will tackle it after GH#1016. | 19:43 | |
| benabik++ indeed. Thanks for pointing that out! | 19:44 | ||
| rurban | We have Sev-* and Pri-* which is kinda mix of severities. github.com/parrot/parrot/issues?la...state=open seems to be a good start | ||
| #548 is indeed a bummer. maybe we should ask nqp/perl6 what hurts them most nowadays (besides performance) | 19:45 | ||
| #1018 is actually a feature, no bug | 19:46 | ||
| Util | Asking nqp/perl6 "what hurts them most nowadays" is always a good idea, IMHO | 19:49 | |
| rurban | I closed some of the thread bugs which are actually features | 19:50 | |
| Util | Last time I asked pmichaud about it, he said these were pain points in Parrot: | 19:53 | |
| 1. calling conventions | |||
| 2. exception handling | |||
| But I think those are painful because of their poor performance. | |||
| rurban | 1. is not fixable for now | ||
| 2. I have no idea about | |||
| Util | Maybe the NQP/Perl 6 team can provide more detail, and we can make tickets for their current pain points. | 19:55 | |
| rurban | 1. is why I gave up on parrot, and rakudo is switching to MoarVM because of this. | ||
| we should ask for fixable bugs, not pain points | 19:56 | ||
| Util | rurban: What would *you* envision as an ideal calling convention? Just curious, as I have been trying to give it thought, and not getting very far. | ||
| rurban | But I have to leave now, getting my glasses. See nothing | 19:57 | |
| Util | rurban: very good point about fixable bugs vs pain points | ||
| rurban: Thanks for attending! | |||
| rurban | My ideal collaing convention is 100% opposite to chromatics vision | ||
| Util | Even if it is not implementable in Parrot, I would love to hear the details sometime. At the very least, it will help clarify my own thinking about the issues and tradeoffs. | 19:58 | |
| rurban | I'd go for cdecl (and did it with p2) c -stack, chromatic goes for CPS in pure bytecode | ||
| CPS is good for exceptions and callcc/yield, but otherwise pretty heavy | 19:59 | ||
| Util | Are you providing continuations in p2? | ||
| rurban | yes, via ucontext | ||
| Util | (as a user-facing feature, I mean) | ||
| rurban | callcc is via the op "here", and yield can go back to any here, or to the scheduler | 20:00 | |
| but I do not switch threads yet | |||
| this is the tricky part | 20:01 | ||
| Util | I see (well, mostly) | ||
| rurban | this=here; do smthng, somewhere else: goto this | ||
| Util | I need to look at some ucontext example code. I will put that on my TODO list, but not for this week. Thanks! | 20:02 | |
| rurban | we cannot use it, we do CPS. it's much easier with CPS | ||
| Util | This week, I will invite NQP/Perl 6 team to speak up about fixable bugs in Parrot. | ||
| rurban: Yes, I understand we (Parrot) cannot use it, but Util's brain can use it. | 20:03 | ||
| rurban | lifecs.likai.org/2010/11/continuati...lling.html | ||
| Util | That is enlightening; thanks! | 20:04 | |
| rurban | That's for my cdecl style. for parrot read up on pure CPS | ||
| fperrad also uses my style (luajit) in his parrot side-project | 20:05 | ||
| Util | Right, I already understand pure CPS, just not continuations-without-pure-CPS | ||
| rurban | it's basically stack saving and switching | ||
| Util | OK | 20:06 | |
| rurban | But a bit more than longjmp, because it needs to handle signals and threads | ||
| So they invented ucontext for a better longjmp | |||
| Util | Sure, like "state" instead of just "stack" | 20:07 | |
| (saving and switching) | |||
| rurban | yes, but on windows you need something else, like fibers | ||
|
20:09
rurban left
|
|||
| Util | Anything else to discuss, from anyone? | 20:09 | |
| Thank you for attending (even via lurking or backscrolling)! | 20:11 | ||
| Meeting adjourned. | 20:12 | ||
|
20:13
Tene joined
21:08
rurban1 joined
21:32
rurban1 joined
23:02
Tene joined
23:15
Tene joined
|
|||