Stories
Slash Boxes
Comments
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)

chromatic
  (email not shown publicly)
http://wgz.org/chromatic/

Blog Information [technorati.com] Profile for chr0matic [technorati.com]

Journal of chromatic (983)

Saturday June 26, 2010
12:07 PM

Perl 6 Design Minutes for 16 June 2010

[ #40419 ]

The Perl 6 design team met by phone on 16 June 2010. Larry, Allison, Patrick, Will, and chromatic attended.

Larry:

  • documented TOP (again), and explained how parsing is initiated and how it actually works
  • series operator (...) now picks a monotonic function when using single characters as endpoints
  • STD can now catch duplicates involving protos as well as onlys
  • STD no longer advises removal of parens on spaceless sub() declaration
  • mostly advised sorear and pmichaud
  • Stefan is finishing the boostrap of the STD parser
  • also working on adding a parallel NFA and DFA engine
  • no, he doesn't want to generate all the states in advance
  • it works faster lazily

Allison:

  • working on chroot environments with something more secure than chroot
  • relevant to building Parrot packages
  • looking at some bugs for Will

Patrick:

  • Rakudo developers decided not to make extra special effort to make a June release of Rakudo Star
  • the calendar works against us
  • the new date for the release is July 29
  • we're I comfortable with hitting that target
  • we won't be happy with the results of moving heaven and earth to release in June
  • there are lots of advantages
  • one disadvantage is not having Rakudo Star at YAPC::NA
  • one big advantage is using the supported Parrot 2.6 release as the basis
  • I'll write a post outlining the plan in the next couple of days
  • otherwise working on lists and interators in Perl 6 and Rakudo
  • after deciding to make iterators immutable, Larry and I realized that solves many problems
  • everything works out as plain as day after that
  • very happy with that design
  • the incorrect assumptions of the old model were pervasive
  • replacing the old pieces is taking a while, which is no surprise
  • this approach feels right though
  • the new branch does things no previous version could do
  • slices work much better, for example
  • metaoperators work properly
  • map is lazy
  • slurpy arguments in lists are lazy by default
  • no weird binding or action at a distance problems
  • plenty of changes to Associative and Positional roles
  • those are now super clean and may be lazy
  • more features work
  • ~30 failing tests (not test files, just tests) now, ~500 last night
  • most of the current failures are minor
  • will try to merge the branch before the release
  • replacing lots of ugly code with fewer lines of elegant code
  • Jonathan and others have worked on lots of other pieces
  • adding plenty of new features
  • looking forward to tomorrow's release

c:

  • editing the Rakudo book
  • moving the Rakudo release date may let us have a printed book available about the same time
  • depends on how much there is left to write
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.