The Perl 6 design team met by phone on 14 April 2010. Larry, Allison, Patrick, Will, and chromatic attended.
Larry:
- on p6l, did a bit of bikeshed paint removal with regard to hyphens vs underscores
- S02 now explicitly disallows both whitespace and unspace in top level of an interpolation
- per spec change, when STD is parsing an interpolation inside quotes and looking for a possible postfix, we now presume that a backslash belongs to the quotes and is not an unspace
- in the src/perl6 directory, renamed all Perl 6
.pm files to .pm6 to avoid confusion
- this was necessary because the implementation of STD translates Perl 6 back to the corresponding Perl 5
- the ambiguity was causing problems with tools such as
NYTProf
Cursor.pmc now prefers .pm6 over .pm in any particular directory when searching for Perl 6 code- as usual lately, most of my hacking work was in improving the human interface of the parser
- STD now distinguishes two final messages: "
Parse failed" vs "Check failed"
- STD now warns on attempts to smartmatch with
True or False
- STD now distinguishes continuable-but-fatal "sorry" messages from immediately fatal "panic" messages
- sorry messages will eventually fail at check time
- changed many of STD's semantic errors to use sorry messages when the parse state is not affected
- modified moritz++'s conflict marker patch to be more like the Clang compiler's behavior
- conflict markers now emit a "sorry" message and continues parsing one side of the conflict
- also fixed a buglet that prevented it from processing the conflict marker if first thing in the file
- while fixing the vws (vertical white space) rule for that, also changed it so that extra lines are now eaten with
\V*\v for consistency
- it had be using
\N*\v
- gimme5 now supports pointing to both ends of missing goal message
- STD's "
Couldn't find final ..." messages now use that capability to point to both ends of the error
- standard quotes now also use the ~ compositor to set the goal and get that behavior
- STD will now dwim
<<op>> ("Texas hypers") better even if op contains angles
- suppressed confusing backtracking on
~<< that produced a misleading quotewords error
- some other patches
- CORE.setting now recognizes the '
note' function
- gimme5 now translates
note to print STDERR
- cleaned up some unneeded locmesses
- Actions.pm now handles prefix metaops without spewing spurious yaml dumps
Allison:
- worked on TT #389
- the actual fix was about two lines
- spent a lot of time fixing tests around it
- didn't like the original two-line fix
- fixed it in IMCC by passing along the
:nsentry flag
- NQP-rx still depends on that feature
- I understood from Patrick that NQP-rx doesn't need that feature
- don't want to launch that before the 2.3 release
- worked on a lot of smaller issues
- worked on the Parrot Developer Virtual Summit
- will talk about some process changes more, as there are details to work out
- will work on GC as the next priority
- useful for Rakudo in general and Parrot concurrency
Patrick:
- catching up on mail and tickets
- should get back to coding in the next couple of days
c:
- worked on the immutable strings branch
- need a couple of changes in the Rakudo binder
- now it's time to convince everyone else it's a worthwhile design change
- going to work on bugfixes
- will try to land the constant string cache
- otherwise, added some optimizations
Will:
- worked on Partcl
- fixed a Parrot bug that broke Rakudo
- does Rakudo need TT #389 in 2.3?
ta ...
thickas on 2010-04-21T07:36:05
I am grateful for any news about P6.
Do you have an Amazon wish list or similar ?
Re:ta ...
chromatic on 2010-04-21T19:01:04
I don't, but as an author and editor one of the nicest things you can do is read and recommend my books. Onyx Neon lists the most recent.
