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 December 13, 2008
05:58 PM

Perl 6 Design Minutes for 03 December 2008

[ #38085 ]

The Perl 6 design team met by phone on 03 December 2008. Allison, Patrick, Jerry, Jesse, and chromatic attended.

Patrick:

  • things are going well
  • we fixed lexicals, which solves a lot of problems for November
  • several people have worked on core features of Parrot to simplify things we're doing in Rakudo
  • especially initializing subroutines, getting signatures correct, and MMD
  • we're waiting for that to land soon
  • Jonathan and I will clean up the compiler code after that
  • it'll be a big improvement
  • that allows us to fix up signature processing to work correctly
  • affects multis and MMD
  • helps fix binding properly
  • we'll probably get list assignment and slicing working after that
  • expect that in the next two weeks
  • otherwise just fixing bugs and adding new features to Rakudo
  • I owe Richard an updated Rakudo roadmap
  • I hope to create something with more narrative prose for the next three months
  • something publishable as a report, rather than a list of milestones
  • it's part of the grant
  • target audience: people who are curious about where Rakudo stands with respect to Christmas
  • I'll also address our plan for Rakudo releases in the new year

c:

  • restarted the Coverity scans and fixed up all of our Tier 1 errors
  • they mostly are resource leaks and bad dereferences
  • we should get bumped up to Tier 2 soon, which is more stringent
  • otherwise, fixed some other bugs
  • cleaned up some memory leaks
  • reviewing Inf/NAN design soon
  • also leading the review of our TODO/SKIP tests, so they all have tickets filed and get un-TODOed and unSKIPped as necessary

Allison:

  • tracking down final test failures on the IO branch
  • just about ready to merge in
  • spent time reviewing Andrew's work in the calling conventions branch
  • it looks like he has context-related failures in PCT
  • spent some time looking at Reini Urban's makeinstall branch
  • hiring an accountant for PaFo
  • reviewing the copyright assignment from TPF to PaFo

Jesse:

  • have you paid attention to the Synopses updates in the Pugs repository?

Patrick:

  • I forgot to mention that they're there now
  • lots of work on S07, Iterators and Laziness

Allison:

  • are we deleting them from the perl.org repository?

Jesse:

  • I thought the plan was to snapshot that occasionally

Patrick:

  • Robert suggested we add an svn:external redirect there
  • I believe he moved the POD to HTML generation to pull from the new location
  • one of the two things needs to happen
  • I moved the entire revision history when I imported them into the Pugs repository
  • it would be good if the website resembled reality somehow
  • the one synopsis not in Pugs is Synopsis 26

Jesse:

  • I talked to Damian about that
  • he's okay with a snapshot going in
  • he'll be working on it further

Jerry:

  • worked on the Perl 6 command-line syntax
  • developing a grammar, more for documentation than implementation
  • lets me test my ideas though
  • that's progressing nicely
  • expect to work on this the remainder of the week
  • getting closer to releasing a draft
  • have not yet been blogging about this
  • it's about time now
  • should I use the Pugs repository for my work in progress?
  • not sure I want to be that visible at this point

Jesse:

  • there's no huge reason to keep the work private

Patrick:

  • you might get a lot of kibbitzing

Jerry:

  • I don't need the distraction

Patrick:

  • the mailing list discussion about S16 is an example
  • that's a productive example
  • but it might be interpreted wrongly if Jerry just ignores that

Jerry:

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.