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)

Thursday July 13, 2006
12:30 AM

Perl 6 Design Notes

[ #30265 ]

Perl 6 Design Team Notes for 12 July 2006

Allison

  • the exceptions design document is done
  • the next bit is the implementation
  • Chip would like to finish namespaces before we implement exceptions
  • I agree

Jesse

  • any response to the final Artistic 2.0?

Allison

  • no
  • I haven't taken it to the OSI for approval and deprecation of Artistic 1.0

Jesse

  • will that have repercussions as Perl 5 is still under Artistic 1.0

Allison

  • it's still approved
  • I'd just like to have it removed from their list of recommended licenses for new projects

Nicholas

  • should h2xs get an update for the new license?

Allison

  • not until Perl 5's license changes

Jesse

  • we shouldn't worry about that until we get the OSI's blessing on AL 2.0

Nicholas

  • haven't done much programming since last time
  • I have an idea about fixing global discussion of inside-out objects in Perl 5
  • that came up on p5p lately
  • have a question about the p5to6 translator
  • how is it?
  • we haven't seen the SoC student on p5p

Larry

  • I've been working with him, he's doing okay
  • he hasn't been mostly interrogating the Perl 5 people
  • he's working with the version I produced, rather than bleadperl
  • just for a stable base
  • feeding the YAML through his program

Nicholas

  • the bleadperl version isn't perfect
  • if you enable it, it fails some regression tests
  • we tweaked things since you added it
  • I hoped that your student would be capable of fixing these things

Larry

  • I think he's better off concentrating on the backend
  • let me concentrate on the MAD part

Nicholas

  • I discouraged people from smoking it as it fails tests
  • I don't want to pre-break our windows

Larry

  • mostly working full-time this week
  • heavy debugging mode right now
  • am watching IRC and thinking about the questions people ask
  • thinking about disallowing constructs that look like postfix operators but aren't
  • did a bit of Synopsis doctoring on that
  • also studying about how to put continuations over a VM that doesn't support them

Patrick

  • out of the office on vacation most of last week
  • have been answering various PGE and parsing questions
  • after YAPC, lots of people are writing parsers using PGE
  • Ruby, JavaScript, various other starting efforts
  • helping them to improve their grammars
  • also asking and answering questions on par-por
  • chatting on IRC
  • answering issues
  • not happy about variable handling in the Perl 6 compiler
  • will do that differently here soon

Jesse

  • have my full draft of the State of Perl 6 roadmap
  • relatively happy with it
  • hope to do some wordsmithing before sending it out

Patrick

  • with the contributor license agreement, is that a bottleneck for getting a commit bit?

Allison

  • as soon as Kevin Tew's contributor agreement arrives in the mail, he'll get it
  • we may not have to wait for it to arrive, but there's potential for some confusion there
  • I can give them a fax number
  • I don't want to put that on the license agreement

Jesse

  • j2.com offers free incoming faxes
  • we could have something generic and webable there

c

  • is there a hackathon space on Sunday?

Jesse

  • when does O'Reilly get access to the conference center?

Allison

  • we do have a room available on Monday and Tuesday

Patrick

  • me and Chip and Jerry at least will hack on Sunday

Allison

  • one of the hotel lobbies might work better
  • the convention center on Sunday might be chaotic

Patrick

  • and there won't be wireless in the convention center

Allison

  • Monday and Tuesday will be a lot easier
  • OSCamp attendees get access to the tutorial snacks and wireless
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.
  • I appreciate the effort you're making to communicate these. At the risk of increasing your burden, it'd be nice if you could add some additional context; maybe a paragraph or two at the beginning describing what people had been doing previously (or what others thought they had been doing).

    Something like

    When we last left our heroes ...
    :-)
    • maybe a paragraph or two at the beginning describing what people had been doing previously (or what others thought they had been doing).

      I'm not chromatic, but as someone who could conceivably be taking the minutes in the future, I think this is pretty tricky. The minutes record what was said on this week's call, and the person writing the minutes has no more information to hand than what you see here. Anyone can read what people were doing previously from previous weeks minutes (once sufficient weeks build

      • I understand. I just want something that would make it clearer to me (and hopefully others) what was going on. Even an opening list of "who was on the call and what they're doing (last week) on Perl6" would help.

        • Chromatic is just picking this up (after the last summarizer moved on to other projects). I think that with him doing this regularly, it should begin to feel more coherent over time.
  • s/global discussion/global destruction/ maybe?
  • I have an idea about fixing global discussion of inside-out objects in Perl 5

    That seems to have got rather lost in translation. It's probably my fault for talking to quickly, and not pausing for breath. What I meant was actually:

    Following investigating troublesome code with clkao [perl.org], I found some issues with the assumptions behind the current attempt at ordering in the global destruction of objects. I don't have any solution (and it's not clear if there is one), and I've not had time to write them up and mai