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)

Tuesday June 15, 2010
08:47 PM

Perl 6 Design Minutes for 12 May 2010

[ #40400 ]

The Perl 6 design team met by phone on 12 May 2010. Larry, Allison, Patrick, and Will attended.

Larry:

  • clarified usage of brackets around infixes
  • added various 128-bit types to the spec; we might make them arbitrarily extensible via role
  • at least LLVM could support this, even to non-powers-of-two sizes
  • modernized the paleolithic grammatical category description in S02
  • STD now uses double-quote rules for interpolating @foo[] into regex
  • STD now gives better message on 1__3
  • added the specced 128-bit types to CORE.setting
  • added minmax function to CORE.setting
  • implemented circumfix:«X Y» as grammar derivation
  • currently only allows a >> inside
  • now also recognizes foofix:("\x[face]") and foofix:("\c[YOUR CHARACTER HERE]") without actually evaluating
  • playing with factoring yaml out of gimme5, since viv is not likely to go that route.
  • mostly just answered a lot of questions on irc
  • egged people on about concurrency issues

Patrick:

  • thought on handling closures properly
  • have a solution, just need some time to implement
  • discussion on changes to CodeString
  • work on compiler toolkit to avoid CodeString, using StringBuilder instead where possible, in PCT, NQP, and rakudo. Pretty easy, no downstream projects block on a deprecation issue
  • after that, lists
  • also been answering questions on interactive mode (REPL) for rakudo et al. (the issue with losing lexicals)

Allison:

  • resolved the git conversation pretty well (for Parrot's repo migration)
  • worked on a pure PEG parser (following the paper), straight PIR, single day; now self-parsing. Interesting project, is lightweight. currently has memoization, but that might not be right for us because of backtracking. With some more effort, could probably handle EBNF form (useful for python)
  • could be setup for developer status for Debian which will improve our packaging status for Debian and Ubuntu

Will:

  • Parrot CodeString performance improvements
  • we're definitely faster in branch, but some feedback from pmichaud should help us clean up the API a bit as well, look for those to hit trunk in the next few days
  • Parrot makefile deps cleanup
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.