Stories
Slash Boxes
Comments

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)

Friday November 03, 2006
03:48 PM

Perl 6 Design Meeting Notes for 01 November 2006

[ #31502 ]

The Perl 6 design team met by phone on 01 November 2006. The attendees were Larry, Damian, Allison, Jesse, Nicholas, and chromatic. Here are the minutes.

Larry:

  • taking it really easy
  • for the same reasons that I'm not going to Brazil
  • making sure I'm here to answer questions that people have

Allison:

  • decided last week to see what it would take to track the Parrot mailing list
  • I look forward to this actually now
  • managed to track the mailing list this week
  • also released a collection of threading ideas
  • not really a first draft
  • enough to get people talking about the ideas
  • going to house sit this Saturday in San Francisco

Damian:

  • things are quiet
  • took most of the week off to recover from the last three months
  • turns out a week isn't quite enough

Larry:

  • I hear you

Damian:

  • didn't actually stop working; that would be silly
  • did scale things back
  • basically caught up on mail and outstanding module issues
  • did read through the multi-dispatch document
  • need to sit down with examples
  • that's the usual way to deal with it

c:

  • trying to get things ready for the Hackathon
  • did more work to get Parrot::Embed to build
  • have I mentioned that I hate C, and cross-platform C, and cross-platform relocatable dynamic linking
  • have some thoughts on concurrency I'll post
  • also keep thinking that Parrot needs a Smalltalky metamodel
  • Perl 6 needs such a thing
  • many languages can use similar customization
  • shoving that down into Parrot will help

Jesse:

  • circulating a list of Parrot milestones and subsystems
  • trying to get responses; not getting many
  • hopefully we'll get a better picture of where things are
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.