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)

Sunday September 17, 2006
03:01 AM

Perl 6 Design Meeting Notes for 13 September 2006

[ #31020 ]

The Perl 6 Design Team met on 13 September. Patrick, Allison, Larry, and chromatic attended. These are the minutes.

Patrick:

  • fixing minor PGE bugs
  • applying small patches
  • decided to do the TGE refactor within the Perl 6 directory
  • saves having to do a branch
  • works out okay when using Perl 6 as the language within the curlies
  • will factor it out later into a standalone tool

Allison:

  • branch or rewrite?

Patrick:

  • it's a copy of the TGE code into the directory and work on it in there

Allison:

  • code fork?

Patrick:

  • yes
  • when everyone is comfortable with the revised version, we can move it back into the TGE-level directory
  • plan to get that done this weekend
  • more to report next week

Larry:

  • getting caught up on everything
  • seems like I get back and everything breaks

Allison:

  • at least the garage didn't flood, this time?

Larry:

  • actually it did
  • battling the usual design fires
  • the latest language thing is the slaughter of all of the metamethods to name them more consistently
  • ref() is gone

Patrick:

  • I highly approve
  • I like this much better

c:

  • can we take it out of Perl 5 too?

Larry:

  • you can at least try
  • renaming skid() and meta() was not difficult to do
  • figuring out which ref() in Pugs is Perl 5 and which is Perl 6 is tough
  • changing meta() to HOW() reveals how overloaded the word "meta" is
  • I think that the new scheme, though it's a little bit quirky, has the benefit that particular words are not heavily overloaded in the current culture
  • we'll see
  • the HOW() object actually stands for Higher Order Working
  • or something like that
  • having fun with that lately
  • my next major outing is to Brazil in November for YAPC::SA

Allison:

  • reviewing a bytecode PDD from Jonathan Worthington this week
  • quite good; I sent him comments
  • still going over the IO PDD
  • hope to spend more time talking to Chip in SF soon
  • I hope that'll be more motivational for both of us
  • it seems to be better when we have more interaction
  • I won't be here next week; I'll be in Brussels
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.