Perl 6 Design Minutes for 15 April 2009

chromatic on 2009-05-30T20:28:13

The Perl 6 design team met by phone on 15 April 2009. Allison, Will, Nicholas, and chromatic attended.

Allison:

  • finished converting Pynie to support Python 3.0
  • checked in a big batch of changes to the Parrot book
  • added a -X command line option to Parrot to add search paths for dynamic extensions
  • still working on the PIR calling conventions
  • NCI is more of a bog than the straight PIR stuff was
  • it's a matter of cleaning up every single place that calls into a PCCMETHOD
  • gradually working my way through those
  • did more work on the Parrot Developer's Guide book cover

c:

  • moving more Parrot code into the proper subdirectories
  • cleaning up the headers
  • will merge in what I have by mid-day Saturday
  • probably won't change any function names; just their locations

Nicholas:

  • happy to see that Dave Mitchell is converging on merging blead to 5.10.1

Will:

  • cleaning the cage
  • trying to enable more warnings and still be clean
  • my biggest current blocker is the language switch to living out of the repository
  • can't build Partcl right now with the 1.0 release
  • I don't see a way yet to make it work
  • will try to get it working with 1.1 this weekend

Allison:

  • do you want it to build off of only an installed Parrot
  • or also with an installed Parrot?

Will:

  • primarily want to work off of an installed release of Parrot
  • a monthly release is fine
  • no problem lagging on features
  • I could build my own copy from HEAD
  • it can't build dynops because the link information is not present in the public parrot_config
  • it relies on the build directory, which is wrong
  • heard some talk recently that was rather incorrect on our current status
  • we could use someone doing marketing to keep our message up to date
  • it's changed some in the past eight years
  • but maybe we need a call for a volunteer to keep our information public and current

Allison:

  • we need to work more on communicating what we're doing
  • I was amazed at how much more response we had from writing a press release and Twittering our 1.0 release

Will:

  • not suggesting any spin
  • I just want to get more facts out there
  • I worked on this with the "This Week in Perl 6" message
  • that sucks from an implementation standpoint
  • I'll try to write more prose for the next time