"Tuesday at 20:30 UTC"
Set by moderator on 20 April 2010.
00:48 particle joined 01:37 bakkdoor joined 02:04 bluescreen joined 06:39 eternaleye joined 06:49 eternaleye joined 09:18 bakkdoor joined 11:55 bluescreen joined 12:24 bluescreen joined 12:37 Whiteknight joined 14:03 eternaleye joined 15:41 bluescreen joined
Coke Rakudo - - Working on some sample code for masak. 15:48
Parrot - - fix editor/skeleton.pir - fix crow
(er, paste failure.)
Rakudo - - Working on some sample code for masak.
Parrot - - fix editor/skeleton.pir - fix crow - add some experimental/deprecated tickets to track status. 15:49
Partcl -
- Trying to get it passing make test again -
- Find a parrot segfault. (fixed by notfound++ & plobsing++)
- However, currently failing all tests. Could use more eyes.
WillDo: - Begin preparing for 2.6 stable release. - rip out recursive make for docs/ - more dependency fixups (and autogeneration)
.EOHORRIBLYFORMATTEDREPORT>
15:55 bluescreen joined, Whiteknight joined, spinclad joined, pmichaud joined, Util joined, Tene joined, cotto joined, wagle joined 16:10 bluescreen joined, Whiteknight joined, spinclad joined, pmichaud joined, Util joined, Tene joined, cotto joined, wagle joined 17:28 mikehh joined
mikehh What I did since my last report: 17:56
* building and testing parrot on amd64/i386, with gcc/g++
* various fixes
* branch testing and some fixes
* fixed perlcritic in ops_pct branch to ignore files with shebang line of #! nqp
What I intend to do in the next week:
* testing and fixing
* documentation
.eor
18:04 NotFound joined
NotFound What I did: 18:06
-parrot
* Added find_codepoint opcode following pmichaud++ suggestion and
discussion on IRC.
* Added experimental function Parrot_str_unescape_string, intended
to sanitize semantic of string literals in pir.
* Shortened generated code for the Object PMC.
* Fixed and updated pbc_checker.
* Added unroll opcode to handle the inner runloop problem in exception
handling.
* Miscellaneous fixes and cleanups.
-winxed
* Always escape non-ascii chars in generated PIR string literals.
* Use the unroll opcode.
* Use pir .const directive for const string.
What I will do:
No plan
EOR 18:07
18:15 cotto_work joined
cotto_work #did: 18:43
- opsc cleanup work
- made ops2c.nqp use Getopt::Obj for arg processing
- switched ops_pct to use ops2c nqp fakecutable to build ops by default
- moved ops.h code out of ops2c.nqp into opsc
- nuked ops2c perl code in ops_pct branch
- updated opsc tests
- found a bug introduced by NotFound++, who quickly fixed it and added a test
- figured out opsrenumber 18:44
- grammar
- fixed most or all misuses of "it's" in svn
- you're welcome
- gsoc
- met with Khairul on Monday, answered some technical questions (extra runcore data and dynpmc building)
- he'll be working in a svn branch as soon as he gets his commit bit
#will do:
- move opsrenumber functionality into opsc
- answer any questions khairul has, do code review
#eor
q1q (and I bet you can guess what it is)
18:45 tcurtis joined 18:56 bluescreen joined 18:58 darbelo joined 19:03 chromatic joined 19:04 khairul joined
Whiteknight * Did: 19:14
- lots of testing
- cut the 2.4.0 "Sulfur Crest" release 19:15
*EOR
19:25 Chandon joined
tcurtis What I've Done: 19:36
* Wrote a blog post about the API of PAST::Pattern and related things.
* Started work on an implementation of Go for Parrot(named Fly, since that's how Parrots go) then stopped upon realizing that all the PCT docs are for PGE and old NQP.
* Asked for a low-level PMC role for things that support invoke VTABLE and got "invokable" thanks to bacek++
* Finished high school.
What I will do:
* Officially graduate high school
* Start coding on PAST::Walker.
* Hopefully get a commit bit
EOR
19:50 bubaflub joined
tcurtis UNEOR the url of mentioned blog post is www.parrot.org/content/past-pattern-matching EORAGAIN 20:00
chromatic I ... didn't get much done and I likely won't until the weekend at the earliest.
darbelo DONE 20:02
- Build cleanups in ops_pct branch.
- Started implementing ucs-4 expect commits by tomorrow.
- Finishing up this week's blog post right now.
TODO
- Finish ucs-4. Turned out ICU isn't as helpful there as I hoped.
- Finish the blog post. Half an hour tops.
- Create an svn branch and start cracking on the grapheme table implementation.
EOR.
Util # Done: 20:09
* Created branch pbc_to_exe_direct_output to reduce memory usage for Rakudo build
= The memory issue was already alleviated by strings improvements in trunk, but this removes the hot-spot for the future.
* Recovered my work on TT#1302 (PIR todo() is frequently misused).
= Commiting tomorrow.
# Plan to do:
* Brain-dump pbc_to_exe knowledge into a Wiki page.
# Blockers: 20:10
* $WORK
.end
20:22 allison joined
allison Between the Ubuntu Developer Summit and preparing for my first exam tomorrow morning, I had no time to work on Parrot this week. 20:26
EOR
cotto_work good afternoon 20:30
20:30 smash joined
mikehh hi all 20:31
chromatic Hello, everyone.
Util Hello
darbelo Hola.
smash hello everyone
allison hiya
NotFound Hola.
chromatic Let's review last week.
2.4.0 is out. How'd that go?
20:32 moritz joined
Coke whiteknight isn't here. 20:32
he didn't complain much. more announcements to go out later. had to back out some last minute commits that came in too close to the release.
darbelo We had a slight hitch with the trunk freeze, IIUC.
chromatic Any thoughts on preventative measures? 20:33
cotto_work talk to fperrad
Coke a git workflow might help avoid it. 20:34
darbelo We might want to use svn ACL features in the future, as a stop-gap before git time is here.
Coke keep an eye on commit log emails if you're the RM is a good temporary workaround.
darbelo That too.
chromatic Other thoughts? 20:35
cotto_work Wouldn't non-technical measures be a better first resort?
moritz I don't think it happens often enough to require thorough investigation yet
darbelo cotto_work: Probably, but I'm no good with those.
chromatic Let's start with non-technical stuff. 20:36
Other review of last week. How'd we do on tests and documentation? 20:37
That doesn't sound promising. 20:38
mikehh some tests were added and I did some testing 20:39
NotFound I added some tests after breaking things because of not having such tests X-)
Util I am working on wiki braindumps of pbc_to_exe, and of the build process in overview, but have nothing posted yet.
chromatic I know Util's looking at a review of some TODO tests. 20:40
Are there other places where we have potential breakage due to the lack of tests?
Util Mostly those are just TODO changing to SKIP, or to conditioned TODOs; it will not improved them beyond that. 20:41
darbelo At least one of the codetests was taught stay out of ext/
That's an improvement. 20:42
mikehh there are some TODO's that pass on i386 but not on amd64 (Ubuntu that is)
chromatic We should make that a design priority, to identify undertested systems when we're working on them.
That goes double for systems that are currently difficult to test.
Util re: potential breakage - should we be running the test suite on installed_parrot? 20:43
chromatic +1
allison yes 20:44
mikehh AFAIK there are problems there
allison yes, it doesn't work at the moment
but it *should* work 20:45
useful for testing packages after installing them too
chromatic Any volunteers to look into it?
NotFound That TODO is flawed, it uses a file build in a particular architecture file for an arch dependant test.
mikehh I'll look at it - how far I'll get is another story 20:46
chromatic Knowing the problems is itself good progress.
Anything else to review from last week?
NotFound We need to build some pbc with the current parrot for that kind of tests, instead of using native_pbc 20:47
mikehh we got a lot of stuff related to codestring moved to trunk
string_builder
Coke that's all in StringBuilder.
right.
NotFound I added the unroll opcode, review and opinions needed.
TT #1635 20:48
chromatic allison and I talked about syntax improvements to PIR to do something similar.
NotFound Probably a helper syntax will need the opcode anyway. 20:50
chromatic I'd like to experiment with that, especially with NQP.
I'm curious to see how it affects Rakudo.
NotFound I'm using it in winxed right now, but don't make specific testing yet. 20:51
chromatic Let's move on to plans for this week. 20:52
What should we focus on?
mikehh ops_pct merge?
cotto_work should be possible 20:53
bacek is there... Almost.
cotto_work just needs opsrenumber
mikehh how almost is that 20:54
cotto_work well, that's more iwbn than a need
chromatic Sounds like that's well under way. Any other priorities? Rakudo needs? 20:55
darbelo jnthn reported failures to the list. Any news on that? 20:56
chromatic Looked related to ICU versions to me.
darbelo Anything our config step could do about it? 20:57
chromatic If it's related to ICU 3 versus ICU 4, config could refuse to use ICU older than 4.x
I don't know that we've verified if it's that, though. 20:58
cotto_work quick unrelated q, if I may
Coke jnthn couldn't duplicate it on his laptop but only his desktop, so it's something versiony.
darbelo Also, we should probably revisit if we want to keep ICU optional or make it mandatory.
cotto_work I'd like to propose that my gsoc student khairul (trac username "khairul") be given a commit bit with me as his mentor. 20:59
darbelo Not right now, but maybe before our next supported release.
chromatic When does coding start?
darbelo The 24th
allison darbelo: last pass through we decided to say that ICU is required for Rakudo, but optional for Parrot 21:00
(to avoid unnecessarily heavy installs of Parrot in resource constrained systems, like, say, mobile phones)
cotto_work afk 20m
darbelo allison: Then rakudo needs to enforce it. I've built rakudo on ICU-less parrots and only noticed after tests failed for me. 21:01
Coke darbelo: that's up to rakudo.
darbelo I'll look into it later and see if I can send them a patch for it.
allison darbelo: should be easy enough for rakudo to check that in their config 21:02
Coke good luck. pretty sure jnthn isn't using icu. =-)
If folks who opened deprecation tickets can make sure they have a summary that says "This is what the new thing looks like", it would be helpful for those trying to close out these old tickets. 21:03
chromatic Any other thoughts on ICU and versions and potential failures, or do we need more data? 21:04
tcurtis moritz is collecting version number data on that, I think.
chromatic Alright. 21:05
Let's move on to GSoC. Do students need commit bits?
Coke I see no problem with giving them bits for the project duration assuming mentors are about. 21:07
(and have already done that for one I think.)
mikehh if they are used responsibly
chromatic Standard lecture: work in your branch, don't break trunk, be responsible. 21:08
allison also fine with it, especially if they're primarily working on branches
(and usual CLA rules)
chromatic Students in the channel: please contact your mentors. Mentors, please shepherd your students.
21:09 Whiteknight joined
chromatic Shall we move on to roadmap review? 21:11
bacek +1 21:12
chromatic allison?
allison no work on GC this week 21:13
that's pretty much it
chromatic I'm blocked on time... and waiting to hear about bacek's fixed-number-of-gcables bitmask marking approach.
bacek chromatic, it's still "sweep" phase. May be little bit faster due reading only bitmask instead of full headers. 21:15
chromatic Can you write up a description of the algorithm and data structures on the wiki?
bacek chromatic, yes, later today. 21:16
chromatic I hope to be able to start implementing something after this weekend.
Any other questions?
Let's wrap it up then. 21:17
bacek Can we deprecate gc_mark_pobj_alive?
chromatic In favor of what?
bacek In favour of PObj* gc_walk_pobj(PObj**)
chromatic For copying/compacting? 21:18
bacek Yes
chromatic I'm not certain that's the right approach. It seems early to do that.
bacek Basically, there is only one place where we have information about PMC memory layout - VTABLE_mark 21:19
And I do want to extend it to provide more information for GC 21:20
(Let's discuss it on #parrot) 21:21
chromatic Okay, thanks everyone. 21:22
tcurtis I have a question. 21:23
chromatic Go ahead.
tcurtis Is there any up-to-date documentation for PCT?
If not, can someone who is knowledegable about it work on some? 21:24
Whiteknight may need to write it
chromatic pmichaud keeps threatening to work on it, but it's definitely not there.
bacek tcurtis, perldoc compilers/pct/src/PAST/Nodes.pir 21:25
Coke tcurtis: they told me the same thing when I asked. there is no good tutorial documentation, methinks.
tcurtis bacek: I was insufficiently specific. I was inquiring about overall documentation from a compiler-writer's perspective, especially concerning grammars. 21:27
Tene tcurtis: the documentation right now is: the PCT source, and the source of other compilers that use PCT. 21:29
bacek tcurtis, I don't think that we have (good) docs for nqp-rx. You can read squaak tutorial for slightly outdated usage of PGE/PCT.
Util has had to clone-and-hack existing NQP, for lack of good NQP docs. 21:30
Coke bacek: that's most unhelpful. =-) 21:31
bacek Coke, at least it covers PCT part :) 21:32
Tene I'd love to work on PCT docs. It's been on my tasklist for a long time. 21:33
Coke tene++
chromatic MEETING OVER 21:51
21:52 NotFound left
Util so noted :) 21:52
22:13 cotto_work left 22:21 darbelo left 22:33 Chandon left 23:43 eternaleye joined