Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

chromatic (983)

  (email not shown publicly)

Blog Information [] Profile for chr0matic []

Journal of chromatic (983)

Friday April 09, 2010
05:07 PM

Perl 6 Design Minutes for 07 April 2010

[ #40306 ]

The Perl 6 design team met by phone on 07 April 2010. Larry, Allison, Patrick, Jerry, Will, and chromatic attended.


  • clarified that object identity from WHICH may not be a mundane value type
  • instead object id's are of type ObjAt to avoid type name collisions.
  • rewrote misleading description of "thunk"
  • made some clarifications of the desired semantics of buffers
  • Buf is primarily a role for dealing compact, unsigned integer arrays in a stringy way
  • but a Buf may be instantiated with other numeric types as well.
  • removed bogus mentions of Buf8, Buf16, Buf32; only the native buf types are sized that way
  • STD now actually parses the insides of tr/// and carps about malformed ranges
  • labels are now stored symbolically as constants rather than types
  • so no coercion routine is added for the name, so it doesn't collide with the function namespace
  • labels are now constants with a unique label type to prevent confusion with ordinary constants
  • module subcompilation now reports the name of the file it's compiling
  • improved various error messages regarding foreach, !!op, $!{}, EOF, and missing punctuation after blocks


  • worked on line number reporting in HLLs
  • no ticket to go on, no good examples
  • didn't make much progress, but didn't have much time
  • sounds like Christoph and chromatic are working on it
  • might look at TT #389


  • you're welcome to it!
  • let me know if you have questions; it's close


  • no travel plans for the next couple of months
  • should have a lot more Parrot time
  • probably time to consider another big project
  • probably GC related


  • updated the progress graph last night
  • up to date as of yesterday
  • Rakudo's passing over 30,000 tests, which is great


  • we have 27 mentors signed up for GSoC
  • a dozen student proposals have come in
  • the admission period ends Friday, so I expect at least a handful more
  • looks like a good year for proposals
  • trying to keep on track of Rakudo development
  • trying to be a go-between for Rakudo and Parrot
  • seems like it's helping Rakudo as Parrot addresses issues that come up


  • Vasily and I fixed the Rakudo performance regression
  • we're going to experiment with immutable strings in a branch
  • expect some notable performance improvements there
  • also worked on the plan to fix line number reporting
  • need a test harness to help identify problems and avoid regressions
  • learned my lesson last time I worked on that....


  • I cringe every time I hear "line numbers"
  • I like what Clang does about highlighting the arguments to functions
  • it'd be nice if we can do similar


  • that'd require more changes to Parrot, but it's doable


  • I just want people to bear it in mind


  • there's no reason we can't have richer annotations
  • our first step is making sure the information we provide them (or they ask for) is accurate
  • is it time to have another big development meeting for Parrot?
  • the release is coming up


  • sounds good
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.