<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>Advogato blog for chromatic</title>
    <link>http://www.advogato.org/person/chromatic/</link>
    <description>Advogato blog for chromatic</description>
    <language>en-us</language>
    <generator>mod_virgule</generator>
    <pubDate>Sat, 25 May 2013 07:00:34 GMT</pubDate>
    <item>
      <pubDate>Sat, 3 Jul 2010 09:09:37 GMT</pubDate>
      <title>Perl 6 Design Minutes for 30 June 2010</title>
      <link>http://www.advogato.org/person/chromatic/diary.html?start=483</link>
      <guid>http://use.perl.org/~chromatic/journal/40433?from=rss</guid>
      <description>&lt;summary type="xhtml"&gt;&lt;div xmlns="http://www.w3.org/1999/xhtml"&gt;&lt;p&gt;The Perl 6 design team met by phone on 30 June 2010.  Allison, Patrick, and chromatic attended.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Allison:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;working on Parrot packages for Debian experimental&lt;/li&gt;&lt;li&gt;seems like a good idea to do that before the 2.6 supported release&lt;/li&gt;&lt;li&gt;there was also a request for Rakudo packages&lt;/li&gt;&lt;li&gt;not sure if I'm the best person to do it&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;Patrick:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;I'm sure we should package Rakudo Star&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;Allison:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;Debian had a packager for those, but I haven't looked at the packages&lt;/li&gt;&lt;li&gt;this'd be an early run of what we'll do with Rakudo Star&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;Patrick:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;we're not quite ready for packaging that yet&lt;/li&gt;&lt;li&gt;maybe a couple of weeks&lt;/li&gt;&lt;li&gt;finished the &lt;code&gt;List&lt;/code&gt; and &lt;code&gt;Iterator&lt;/code&gt; types for the #30 release&lt;/li&gt;&lt;li&gt;adjusted Rakudo's &lt;code&gt;Associative&lt;/code&gt; and &lt;code&gt;Positional&lt;/code&gt; roles&lt;/li&gt;&lt;li&gt;much cleaner implementation now&lt;/li&gt;&lt;li&gt;that'll require a few small spec changes&lt;/li&gt;&lt;li&gt;redid Rakudo's container types&lt;/li&gt;&lt;li&gt;more robust&lt;/li&gt;&lt;li&gt;preparing for autovivification of hashes and arrays&lt;/li&gt;&lt;li&gt;expect to finish those in the next couple of days&lt;/li&gt;&lt;li&gt;there was no container model previously; the code was consequently crufty&lt;/li&gt;&lt;li&gt;lots of cleanup of incorrect assumptions&lt;/li&gt;&lt;li&gt;Rakudo lists are now properly lazy&lt;/li&gt;&lt;li&gt;comment syntax fixed&lt;/li&gt;&lt;li&gt;ROADMAP updated&lt;/li&gt;&lt;li&gt;fixed the meaning of &lt;code&gt;Nil&lt;/code&gt;; it's defined, not undefined&lt;/li&gt;&lt;li&gt;added the sink prefix (?)&lt;/li&gt;&lt;li&gt;fixed setting of &lt;code&gt;$!&lt;/code&gt; &lt;/li&gt;&lt;li&gt;started fixing bugs and closing tickets on Monday, did 15 or 20&lt;/li&gt;&lt;li&gt;mostly already fixed in the previous couple of weeks&lt;/li&gt;&lt;li&gt;looking at the implementation of the series operator&lt;/li&gt;&lt;li&gt;spec is self-contradictory or ambiguous or both&lt;/li&gt;&lt;li&gt;waiting for Larry's clarification&lt;/li&gt;&lt;li&gt;fixed a bug in &lt;code&gt;$*ARGFILES&lt;/code&gt; &lt;/li&gt;&lt;li&gt;had a nice contribution of that implementation last week&lt;/li&gt;&lt;li&gt;that behavior works on any set of files, not just those on the command line&lt;/li&gt;&lt;li&gt;working on autoviv&lt;/li&gt;&lt;li&gt;have some regex backtracking bugs to fix&lt;/li&gt;&lt;li&gt;will work on closures after that&lt;/li&gt;&lt;li&gt;put together three new YAPC presentations&lt;/li&gt;&lt;li&gt;the Rakudo Star presentation will become a video cast or a blog post or both&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;c:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;worked on a slew of Parrot optimizations for Rakudo&lt;/li&gt;&lt;li&gt;have a few more to go&lt;/li&gt;&lt;li&gt;might have to create a Rakudo branch temporarily&lt;/li&gt;&lt;li&gt;will try to help merge the new GC&lt;/li&gt;&lt;li&gt;working on a metamodel for Parrot objects, informed by Perl 6 and Moose&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;/summary&gt;</description>
    </item>
    <item>
      <pubDate>Tue, 29 Jun 2010 00:11:27 GMT</pubDate>
      <title>Modern Perl: The (Draft) Book</title>
      <link>http://www.advogato.org/person/chromatic/diary.html?start=482</link>
      <guid>http://use.perl.org/~chromatic/journal/40423?from=rss</guid>
      <description>&lt;summary type="xhtml"&gt;&lt;div xmlns="http://www.w3.org/1999/xhtml"&gt;&lt;p&gt;This took longer than I expected, but &lt;a href="http://www.modernperlbooks.com/mt/2010/06/modern-perl-the-book-the-draft.html" &gt;the draft of the Modern Perl book is available for review&lt;/a&gt;.  I'm especially interested in hearing from people who don't consider themselves expert Perl 5 programmers.  The goal of the book is to explain how Perl 5 works (and how to write Perl 5 effectively) to help novices become adepts.&lt;/p&gt;&lt;/div&gt;&lt;/summary&gt;</description>
    </item>
    <item>
      <pubDate>Sat, 26 Jun 2010 17:09:43 GMT</pubDate>
      <title>Perl 6 Design Minutes for 16 June 2010</title>
      <link>http://www.advogato.org/person/chromatic/diary.html?start=481</link>
      <guid>http://use.perl.org/~chromatic/journal/40419?from=rss</guid>
      <description>&lt;summary type="xhtml"&gt;&lt;div xmlns="http://www.w3.org/1999/xhtml"&gt;&lt;p&gt;The Perl 6 design team met by phone on 16 June 2010.  Larry, Allison, Patrick, Will, and chromatic attended.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Larry:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;documented &lt;code&gt;TOP&lt;/code&gt; (again), and explained how parsing is initiated and how it actually works&lt;/li&gt;&lt;li&gt;series operator (&lt;code&gt;...&lt;/code&gt;) now picks a monotonic function when using single characters as endpoints&lt;/li&gt;&lt;li&gt;STD can now catch duplicates involving &lt;code&gt;proto&lt;/code&gt;s as well as &lt;code&gt;only&lt;/code&gt;s&lt;/li&gt;&lt;li&gt;STD no longer advises removal of parens on spaceless &lt;code&gt;sub()&lt;/code&gt; declaration&lt;/li&gt;&lt;li&gt;mostly advised sorear and pmichaud&lt;/li&gt;&lt;li&gt;Stefan is finishing the boostrap of the STD parser&lt;/li&gt;&lt;li&gt;also working on adding a parallel NFA and DFA engine&lt;/li&gt;&lt;li&gt;no, he doesn't want to generate all the states in advance&lt;/li&gt;&lt;li&gt;it works faster lazily&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;Allison:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;working on chroot environments with something more secure than chroot&lt;/li&gt;&lt;li&gt;relevant to building Parrot packages&lt;/li&gt;&lt;li&gt;looking at some bugs for Will&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;Patrick:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;Rakudo developers decided not to make extra special effort to make a June release of Rakudo Star&lt;/li&gt;&lt;li&gt;the calendar works against us&lt;/li&gt;&lt;li&gt;the new date for the release is July 29&lt;/li&gt;&lt;li&gt;we're I comfortable with hitting that target&lt;/li&gt;&lt;li&gt;we won't be happy with the results of moving heaven and earth to release in June&lt;/li&gt;&lt;li&gt;there are lots of advantages&lt;/li&gt;&lt;li&gt;one disadvantage is not having Rakudo Star at YAPC::NA&lt;/li&gt;&lt;li&gt;one big advantage is using the supported Parrot 2.6 release as the basis&lt;/li&gt;&lt;li&gt;I'll write a post outlining the plan in the next couple of days&lt;/li&gt;&lt;li&gt;otherwise working on lists and interators in Perl 6 and Rakudo&lt;/li&gt;&lt;li&gt;after deciding to make iterators immutable, Larry and I realized that solves many problems&lt;/li&gt;&lt;li&gt;everything works out as plain as day after that&lt;/li&gt;&lt;li&gt;very happy with that design&lt;/li&gt;&lt;li&gt;the incorrect assumptions of the old model were pervasive&lt;/li&gt;&lt;li&gt;replacing the old pieces is taking a while, which is no surprise&lt;/li&gt;&lt;li&gt;this approach feels right though&lt;/li&gt;&lt;li&gt;the new branch does things no previous version could do&lt;/li&gt;&lt;li&gt;slices work much better, for example&lt;/li&gt;&lt;li&gt;metaoperators work properly&lt;/li&gt;&lt;li&gt;map is lazy&lt;/li&gt;&lt;li&gt;slurpy arguments in lists are lazy by default&lt;/li&gt;&lt;li&gt;no weird binding or action at a distance problems&lt;/li&gt;&lt;li&gt;plenty of changes to &lt;code&gt;Associative&lt;/code&gt; and &lt;code&gt;Positional&lt;/code&gt; roles&lt;/li&gt;&lt;li&gt;those are now super clean and may be lazy&lt;/li&gt;&lt;li&gt;more features work&lt;/li&gt;&lt;li&gt;~30 failing tests (not test files, just tests) now, ~500 last night&lt;/li&gt;&lt;li&gt;most of the current failures are minor&lt;/li&gt;&lt;li&gt;will try to merge the branch before the release&lt;/li&gt;&lt;li&gt;replacing lots of ugly code with fewer lines of elegant code&lt;/li&gt;&lt;li&gt;Jonathan and others have worked on lots of other pieces&lt;/li&gt;&lt;li&gt;adding plenty of new features&lt;/li&gt;&lt;li&gt;looking forward to tomorrow's release&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;c:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;editing the Rakudo book&lt;/li&gt;&lt;li&gt;moving the Rakudo release date may let us have a printed book available about the same time&lt;/li&gt;&lt;li&gt;depends on how much there is left to write&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;/summary&gt;</description>
    </item>
    <item>
      <pubDate>Thu, 24 Jun 2010 13:16:02 GMT</pubDate>
      <title>Perl 6 Design Minutes for 09 June 2010</title>
      <link>http://www.advogato.org/person/chromatic/diary.html?start=480</link>
      <guid>http://use.perl.org/~chromatic/journal/40415?from=rss</guid>
      <description>&lt;p&gt;The Perl 6 design team met by phone on 09 June 2010.  Larry, Allison, Patrick, and chromatic attended.&lt;/p&gt;&lt;p&gt; &lt;strong&gt;Larry:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;not much spec change this week&lt;/li&gt;&lt;li&gt;figured out a syntax for a regex block to return more than one cursor&lt;/li&gt;&lt;li&gt;based on &lt;code&gt;gather&lt;/code&gt;/&lt;code&gt;take&lt;/code&gt; &lt;/li&gt;&lt;li&gt;in STD hacking, continued to assist Stefan O'Rear in getting STD bootstrapped via viv&lt;/li&gt;&lt;li&gt;now that it's bootstrapped, we're refactoring things that make sense now&lt;/li&gt;&lt;li&gt;we're now starting to move bits of Cursor code from Perl 5 into Perl 6&lt;/li&gt;&lt;li&gt;refactoring the grammar for sanity of design&lt;/li&gt;&lt;li&gt;started upgrading STD to normal Perl 6 syntax where it previously catered to &lt;code&gt;gimme5&lt;/code&gt;'s limitations&lt;/li&gt;&lt;li&gt;for example, switched STD's old&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;.&amp;lt;_from&amp;gt;&lt;/code&gt; and&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;.&amp;lt;_pos&amp;gt;&lt;/code&gt; hash lookups to using&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;.from&lt;/code&gt; and&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;.pos&lt;/code&gt; accessors&lt;/li&gt;&lt;li&gt;started the prep work for moving &lt;code&gt;EXPR&lt;/code&gt; out of &lt;code&gt;STD&lt;/code&gt; to make it generally available to any grammar wanting operator precedence&lt;/li&gt;&lt;li&gt;in STD parsing, made Perl 5 &lt;code&gt;$&amp;lt;&lt;/code&gt; detection have a longer token to avoid confusion with match variables&lt;/li&gt;&lt;li&gt;STD no longer attempts two-terms detection on &lt;code&gt;infix_circumfix_meta_operator&lt;/code&gt; &lt;/li&gt;&lt;li&gt;STD now parses &lt;code&gt;&amp;gt;&amp;gt;R~&amp;lt;&amp;lt;&lt;/code&gt; correctly, or at least dwimmily&lt;/li&gt;&lt;li&gt;STD doesn't complain about P5isms in &lt;code&gt;printf&lt;/code&gt; formats like &lt;code&gt;"%{$count}s"&lt;/code&gt; &lt;/li&gt;&lt;li&gt;STD was parsing&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;/m&lt;/code&gt; and&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;/s&lt;/code&gt; with the opposite semantics&lt;/li&gt;&lt;li&gt; &lt;code&gt;termish&lt;/code&gt; now localizes &lt;code&gt;$*MULTINESS&lt;/code&gt; in its scope so that inner declarations aren't accidentally multified&lt;/li&gt;&lt;li&gt;STD now carps about &lt;code&gt;package Foo;&lt;/code&gt; as a Perl 5 construct&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;Allison:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;talked to Chris Shiflett, a PHP developer, on someone from the PHP community to sit on the Parrot board&lt;/li&gt;&lt;li&gt;will be in the US for a few weeks&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;Patrick:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;working on list simplification&lt;/li&gt;&lt;li&gt;had a couple of breakthrough ideas on Monday&lt;/li&gt;&lt;li&gt;working on the implementation now&lt;/li&gt;&lt;li&gt;worked out inversion lists for character class matching in regexes&lt;/li&gt;&lt;li&gt;will make them faster, especially with long ranges of character classes&lt;/li&gt;&lt;li&gt;fixed a half-dozen tickets in RT&lt;/li&gt;&lt;li&gt;fixed Rakudo hash constructors&lt;/li&gt;&lt;li&gt;fixed an intermittent bug with colon-pair signatures&lt;/li&gt;&lt;li&gt;two possible parses exist in STD, but we removed an unneeded one in Rakudo&lt;/li&gt;&lt;li&gt;fixed a bug with Parrot's &lt;code&gt;exit&lt;/code&gt; opcode&lt;/li&gt;&lt;li&gt;NQP and PAST needed an update not to cheat with PASM constants&lt;/li&gt;&lt;li&gt;I fixed that too&lt;/li&gt;&lt;li&gt;Vasily added multisub and multimethod support to NQP, that was a big plus&lt;/li&gt;&lt;li&gt;fixed the &lt;code&gt;**&lt;/code&gt; quantifier in regexes to understand surrounding whitespace&lt;/li&gt;&lt;li&gt;regex engine tried to match beyond the end of a string, so I added guards for that&lt;/li&gt;&lt;li&gt;will work on lists furiously before the next release&lt;/li&gt;&lt;li&gt;I don't think it'll take long&lt;/li&gt;&lt;li&gt;closures are next, hope to have those in place by the weekend&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;c:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;released a new version of Pod::PseudoPod::LaTeX to support the various books in progress&lt;/li&gt;&lt;/ul&gt;</description>
    </item>
    <item>
      <pubDate>Tue, 22 Jun 2010 02:13:44 GMT</pubDate>
      <title>Perl 6 Design Minutes for 02 June 2010</title>
      <link>http://www.advogato.org/person/chromatic/diary.html?start=479</link>
      <guid>http://use.perl.org/~chromatic/journal/40410?from=rss</guid>
      <description>&lt;summary type="xhtml"&gt;&lt;div xmlns="http://www.w3.org/1999/xhtml"&gt;&lt;p&gt;The Perl 6 design team met by phone on 02 June 2010.  Larry, Allison, Patrick, Will, and chromatic attended.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Larry:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;mostly, I supported sorear in bootstrapping STD to use &lt;code&gt;viv&lt;/code&gt; instead of &lt;code&gt;gimme5&lt;/code&gt; &lt;/li&gt;&lt;li&gt;his stage 2 and stage 3 now output identical Perl 5 versions of STD&lt;/li&gt;&lt;li&gt;produces a huge amount of warnings&lt;/li&gt;&lt;li&gt;appears to require Perl 5.12 at the moment&lt;/li&gt;&lt;li&gt;working on both of those&lt;/li&gt;&lt;li&gt;S03 refines hyper dwimminess to be more like APL, with modular semantics&lt;/li&gt;&lt;li&gt;S02 refines &lt;code&gt;Blob&lt;/code&gt;s to simply be immutable &lt;code&gt;Buf&lt;/code&gt;s, with similar generic characteristics&lt;/li&gt;&lt;li&gt;S02 now describes native &lt;code&gt;blob&lt;/code&gt; types&lt;/li&gt;&lt;li&gt;implemented post-declaration checks for &lt;code&gt;BEGIN&lt;/code&gt; and &lt;code&gt;use&lt;/code&gt;, since those can't wait for end of file&lt;/li&gt;&lt;li&gt;STD no longer loses existing bindings when we go to a sublanguage&lt;/li&gt;&lt;li&gt;STD now uses &lt;code&gt;$*GOAL&lt;/code&gt; variable only as informative, never as a "stopper"&lt;/li&gt;&lt;li&gt;instead, we create a &lt;code&gt;&amp;lt;stopper&amp;gt;&lt;/code&gt; rule for &lt;code&gt;$*GOAL&lt;/code&gt; if necessary&lt;/li&gt;&lt;li&gt;can check for that only, instead of that or &lt;code&gt;$*GOAL&lt;/code&gt; &lt;/li&gt;&lt;li&gt;answering lots of questions on how STD and &lt;code&gt;viv&lt;/code&gt; work besides that&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;Allison:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;did a lot of research on graph color algorithms for register usage algorithms&lt;/li&gt;&lt;li&gt;will finish my finals on Monday&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;Will:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;trying to herd the discussion of dynop libraries&lt;/li&gt;&lt;li&gt;a recent branch to close an old ticket broke a lot of assumptions&lt;/li&gt;&lt;li&gt;some bugs have become more visible because of these changes&lt;/li&gt;&lt;li&gt;hope to get that cleaned up this week&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;Allison:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;I liked your suggestion of bringing back the &lt;code&gt;getstderr&lt;/code&gt; and related opcodes&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;Will:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;trying to resurrect Partcl&lt;/li&gt;&lt;li&gt;stuck on a TT #389 closing issue&lt;/li&gt;&lt;li&gt;not sure how to fix that, the way things are now&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;Patrick:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;working on the iterator and list design&lt;/li&gt;&lt;li&gt;brainstorming the implementation&lt;/li&gt;&lt;li&gt;will implement somethine one way or another this week&lt;/li&gt;&lt;li&gt;people keep implementing workarounds for the current system&lt;/li&gt;&lt;li&gt;they'll bite us eventually&lt;/li&gt;&lt;li&gt;Moritz and I worked on making the regex engine returning real Perl 6 objects&lt;/li&gt;&lt;li&gt;that mostly works&lt;/li&gt;&lt;li&gt;exposes some places where lists don't work exactly right&lt;/li&gt;&lt;li&gt;the workarounds there made me replan the list and iterator implementation&lt;/li&gt;&lt;li&gt;answered some questions online&lt;/li&gt;&lt;li&gt;Jonathan added a better backtrace algorithm for Rakudo&lt;/li&gt;&lt;li&gt;reports Perl 6 source lines instead of PIR lines&lt;/li&gt;&lt;li&gt;I'll review his code&lt;/li&gt;&lt;li&gt;think I can borrow it for NQP for all HLLs&lt;/li&gt;&lt;li&gt;Jonathan reports that it was a lot easier in NQP than PIR&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;c:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;trying to answer a few Parrot design questions&lt;/li&gt;&lt;li&gt;looking at the continuation of design from Perl 1 - 4 to Perl 5 and Perl 6&lt;/li&gt;&lt;li&gt;hope to have coding time soon&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;/summary&gt;</description>
    </item>
    <item>
      <pubDate>Sun, 20 Jun 2010 20:11:17 GMT</pubDate>
      <title>Perl 6 Design Minutes for 26 May 2010</title>
      <link>http://www.advogato.org/person/chromatic/diary.html?start=478</link>
      <guid>http://use.perl.org/~chromatic/journal/40408?from=rss</guid>
      <description>&lt;p&gt;The Perl 6 design team met by phone on 26 May 2010.  Larry, Allison,
Patrick, Will, and chromatic attended.&lt;/p&gt;&lt;p&gt; &lt;strong&gt;Larry:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;:()&lt;/code&gt; syntax is now always signature&lt;/li&gt;&lt;li&gt;we now use &lt;code&gt;foofix:[...]&lt;/code&gt; as the general op form instead of &lt;code&gt;foofix:(...)&lt;/code&gt; &lt;/li&gt;&lt;li&gt;refactored the sematics of&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;:nth&lt;/code&gt; and&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;:x&lt;/code&gt; &lt;/li&gt;&lt;li&gt;&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;:nth()&lt;/code&gt; now only ever takes a monotonically increasing list&lt;/li&gt;&lt;li&gt;S03 now explains how "not-raising" works on &lt;code&gt;!=&lt;/code&gt; and &lt;code&gt;ne&lt;/code&gt; &lt;/li&gt;&lt;li&gt;it now basically matches the intuitions of an English speaker via HOP definition of negate metaop&lt;/li&gt;&lt;li&gt;STD sometimes didn't require semi between statements&lt;/li&gt;&lt;li&gt;statement modifiers are expression terminators but not valid statement terminators&lt;/li&gt;&lt;li&gt;an unexpected statement modifier word like &lt;code&gt;if&lt;/code&gt; could terminate one statement and start another&lt;/li&gt;&lt;li&gt;fixed up backslashes in character classes to allow &lt;code&gt;\s&lt;/code&gt; etc and reject &lt;code&gt;\u&lt;/code&gt; etc&lt;/li&gt;&lt;li&gt;STD was accidentally using the same lexpad for different multis&lt;/li&gt;&lt;li&gt;Cursor now treats&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;:()&lt;/code&gt; on name extension as a signature always, never as a categorical&lt;/li&gt;&lt;li&gt;we shouldn't introduce the stopper for circumfix until we're in the circumfix, or we can't use the same char on both ends&lt;/li&gt;&lt;li&gt;placeholder messages error messages are now much more informative and correct&lt;/li&gt;&lt;li&gt;we now disallow use of placeholder after same variable has been used as a non-placeholder, even for an outer reference&lt;/li&gt;&lt;li&gt;renamed add_macro (which it doesn't) to add_categorical (which it does)&lt;/li&gt;&lt;li&gt;participating frequently in discussions on semantics both on irc and p6l&lt;/li&gt;&lt;li&gt;working closely with sorear++ as he brings viv closer to bootstrapping, yay!&lt;/li&gt;&lt;li&gt;soon can bootstrap past gimme5&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;Allison:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;worked on Pynie this week in my limited spare time&lt;/li&gt;&lt;li&gt;one goal is to generate the parser directly from the Python grammar&lt;/li&gt;&lt;li&gt;wrote a small, lightweight PEG parser which generates a match tree from the Python 3 grammar&lt;/li&gt;&lt;li&gt;can generate a lexer directly&lt;/li&gt;&lt;li&gt;right now it creates a parse tree&lt;/li&gt;&lt;li&gt;looks similar to the match nodes of NQP-rx&lt;/li&gt;&lt;li&gt;dumps out a tree to the PIR parser&lt;/li&gt;&lt;li&gt;working on PaFo elections for next year, but trying to delegate those&lt;/li&gt;&lt;li&gt;will have more time after June 7&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;Will:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;working on Perl 6 advent tests&lt;/li&gt;&lt;li&gt;many more people are doing more work than me&lt;/li&gt;&lt;li&gt;liasing with Rakudo folks for any important Parrot bugs before the Rakudo Star release&lt;/li&gt;&lt;li&gt;my current direction there is "don't break anything"&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;Patrick:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;sorear added hash flattening to NQP&lt;/li&gt;&lt;li&gt;lots of work on closures in PAST and NQP&lt;/li&gt;&lt;li&gt;they properly clone&lt;/li&gt;&lt;li&gt;fixes some lexical problems&lt;/li&gt;&lt;li&gt;need to get that to work in Rakudo&lt;/li&gt;&lt;li&gt;that's tougher; Rakudo has to wrap Parrot subs&lt;/li&gt;&lt;li&gt;wrapper object needs cloning as well, along with its attributes&lt;/li&gt;&lt;li&gt;we'll add a new PAST node type to help&lt;/li&gt;&lt;li&gt;that node understands contexts&lt;/li&gt;&lt;li&gt;essentially a way to add void context optimizations to your AST&lt;/li&gt;&lt;li&gt;that solves many problems in Rakudo beyond closures&lt;/li&gt;&lt;li&gt;added a setting into NQP along with its test suite&lt;/li&gt;&lt;li&gt;not automatically loaded, but available&lt;/li&gt;&lt;li&gt;contains standard hash and array methods&lt;/li&gt;&lt;li&gt;Parrot's ops2c project uses those&lt;/li&gt;&lt;li&gt;other people can update and enhance that setting as necessary&lt;/li&gt;&lt;li&gt;NQP also has the ability to parse type names&lt;/li&gt;&lt;li&gt;NQP doesn't do anything with them yet&lt;/li&gt;&lt;li&gt;eventually they'll allow the use of multis&lt;/li&gt;&lt;li&gt;cleaning up some NQP bugs regarding lexicals and package storage of subs&lt;/li&gt;&lt;li&gt;Bruce Keeler enabled variable interpolations in regexes&lt;/li&gt;&lt;li&gt;working on some refactorings to simplify that approach&lt;/li&gt;&lt;li&gt;works in NQP and Rakudo now&lt;/li&gt;&lt;li&gt;that's a feature we've never had before&lt;/li&gt;&lt;li&gt;Rakudo's REPL now works better, thanks to sorear&lt;/li&gt;&lt;li&gt;HLLCompiler now written more in NQP as part of that&lt;/li&gt;&lt;li&gt;NQP now can do &lt;code&gt;eval&lt;/code&gt; &lt;/li&gt;&lt;li&gt;NQP remembers lexicals in interactive mode now&lt;/li&gt;&lt;li&gt;adding that to Rakudo is more complex&lt;/li&gt;&lt;li&gt;working on that&lt;/li&gt;&lt;li&gt;pleased with the progress on #perl6&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;c:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;reviewing long term plans for GC and Lorito&lt;/li&gt;&lt;li&gt;should have more time free soon&lt;/li&gt;&lt;/ul&gt;</description>
    </item>
    <item>
      <pubDate>Wed, 16 Jun 2010 22:10:54 GMT</pubDate>
      <title>Perl 6 Design Minutes for 19 May 2010</title>
      <link>http://www.advogato.org/person/chromatic/diary.html?start=477</link>
      <guid>http://use.perl.org/~chromatic/journal/40401?from=rss</guid>
      <description>&lt;p&gt;The Perl 6 design team met by phone on 19 May 2010.  Larry, Will, and
chromatic attended.  Patrick added his notes later.&lt;/p&gt;&lt;p&gt; &lt;strong&gt;Larry:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;S03 makes more explicit that doctrine that &lt;code&gt;~~&lt;/code&gt; topicalizes, and removes smartmatch table fossils that automatically fall out from that&lt;/li&gt;&lt;li&gt;S05 renames 'accent' to 'mark' for better Unicode conformance&lt;/li&gt;&lt;li&gt;&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;:a&lt;/code&gt; and&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;:aa&lt;/code&gt; changed to&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;:m&lt;/code&gt; and&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;:mm&lt;/code&gt; &lt;/li&gt;&lt;li&gt;S05 disrequires retroactive semantics on&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;:samecase&lt;/code&gt; and&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;:samemark&lt;/code&gt; &lt;/li&gt;&lt;li&gt;the method form must now explicitly add case or mark modifiers to the pattern&lt;/li&gt;&lt;li&gt;regularized &lt;code&gt;mm//&lt;/code&gt; to &lt;code&gt;ms//&lt;/code&gt; to avoid confusion with new&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;:m&lt;/code&gt; ignoremark option&lt;/li&gt;&lt;li&gt;STD now does a bit better at diagnosing bogus &lt;code&gt;??!!&lt;/code&gt; constructs of various sorts&lt;/li&gt;&lt;li&gt;STD now correctly adds operators to symbol tables as subs&lt;/li&gt;&lt;li&gt; &lt;code&gt;CORE.setting&lt;/code&gt; now has protos of all the operators so they can be recognized as subs too&lt;/li&gt;&lt;li&gt;Cursor now canonicalize operator names in the symbol table&lt;/li&gt;&lt;li&gt;btw, not quite like specced&lt;/li&gt;&lt;li&gt;STD now reads user's mind on '&lt;code&gt;Str $toto&lt;/code&gt;' to intuit missing declarator&lt;/li&gt;&lt;li&gt;STD now properly diagnoses a typename between routine declarator and sub name&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;Will:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;working on code for Carl Masak, trying to get his poker code example running on Rakudo&lt;/li&gt;&lt;li&gt;both fun and frustrating&lt;/li&gt;&lt;li&gt;some stuff doesn't quite work yet&lt;/li&gt;&lt;li&gt;going through the Advent examples&lt;/li&gt;&lt;li&gt;adding them to spectests&lt;/li&gt;&lt;li&gt;make sure we won't regress on such public examples&lt;/li&gt;&lt;li&gt;other people are helping with that now&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;c:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;will get back to editing the Rakudo book soon&lt;/li&gt;&lt;li&gt;hope to have it in print by YAPC, but no guarantee&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;Patrick:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;fixed closures in NQP, as a precursor for fixing them in Rakudo&lt;/li&gt;&lt;li&gt;worked with sorear on REPL in Rakudo and PCT in general&lt;/li&gt;&lt;li&gt;ported the NQP "standard library" done by japhb++, bacek++, and many others into the nqp-rx repository and made it part of the standard build sequence for nqp and Parrot&lt;/li&gt;&lt;li&gt;decided we need a new "context sensitive" node type in PAST, will be used to create proper closures and to handle sink context&lt;/li&gt;&lt;li&gt;worked with bacek on adding better multimethod support to PAST and nqp-rx&lt;/li&gt;&lt;li&gt;discovered a problem with lexical subs in NQP being automatically entered into the package namespace (and some existing code relying on this behavior)&lt;/li&gt;&lt;li&gt;did some initial fixes to at least get things entered properly, but a complete fix may require a deprecation cycle&lt;/li&gt;&lt;li&gt;plan to review others' patches this week&lt;/li&gt;&lt;li&gt;plan to fix REPL, closures, and sink context in Rakudo (since those are currently large pain points)&lt;/li&gt;&lt;li&gt;plan to work on loops and iterators after that&lt;/li&gt;&lt;/ul&gt;</description>
    </item>
    <item>
      <pubDate>Wed, 16 Jun 2010 02:06:23 GMT</pubDate>
      <title>Perl 6 Design Minutes for 12 May 2010</title>
      <link>http://www.advogato.org/person/chromatic/diary.html?start=476</link>
      <guid>http://use.perl.org/~chromatic/journal/40400?from=rss</guid>
      <description>&lt;summary type="xhtml"&gt;&lt;div xmlns="http://www.w3.org/1999/xhtml"&gt;&lt;p&gt;The Perl 6 design team met by phone on 12 May 2010.  Larry, Allison, Patrick, and Will attended.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Larry:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;clarified usage of brackets around infixes&lt;/li&gt;&lt;li&gt;added various 128-bit types to the spec; we might make them arbitrarily extensible via role&lt;/li&gt;&lt;li&gt;at least LLVM could support this, even to non-powers-of-two sizes&lt;/li&gt;&lt;li&gt;modernized the paleolithic grammatical category description in S02&lt;/li&gt;&lt;li&gt;STD now uses double-quote rules for interpolating &lt;code&gt;@foo[]&lt;/code&gt; into regex&lt;/li&gt;&lt;li&gt;STD now gives better message on &lt;code&gt;1__3&lt;/code&gt; &lt;/li&gt;&lt;li&gt;added the specced 128-bit types to CORE.setting&lt;/li&gt;&lt;li&gt;added &lt;code&gt;minmax&lt;/code&gt; function to CORE.setting&lt;/li&gt;&lt;li&gt;implemented &lt;code&gt;circumfix:&amp;#xAB;X Y&amp;#xBB;&lt;/code&gt; as grammar derivation&lt;/li&gt;&lt;li&gt;currently only allows a &lt;code&gt; &amp;gt;&amp;gt; inside&lt;/code&gt;&lt;/li&gt;&lt;li&gt;now also recognizes &lt;code&gt;foofix:("\x[face]")&lt;/code&gt; and &lt;code&gt;foofix:("\c[YOUR CHARACTER HERE]")&lt;/code&gt; without actually evaluating&lt;/li&gt;&lt;li&gt;playing with factoring &lt;code&gt;yaml&lt;/code&gt; out of &lt;code&gt;gimme5&lt;/code&gt;, since &lt;code&gt;viv&lt;/code&gt; is not likely to go that route.&lt;/li&gt;&lt;li&gt;mostly just answered a lot of questions on irc&lt;/li&gt;&lt;li&gt;egged people on about concurrency issues&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;Patrick:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;thought on handling closures properly&lt;/li&gt;&lt;li&gt;have a solution, just need some time to implement&lt;/li&gt;&lt;li&gt;discussion on changes to CodeString&lt;/li&gt;&lt;li&gt;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&lt;/li&gt;&lt;li&gt;after that, lists&lt;/li&gt;&lt;li&gt;also been answering questions on interactive mode (REPL) for rakudo et al. (the issue with losing lexicals)&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;Allison:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;resolved the git conversation pretty well (for Parrot's repo migration)&lt;/li&gt;&lt;li&gt;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)&lt;/li&gt;&lt;li&gt;could be setup for developer status for Debian which will improve our packaging status for Debian and Ubuntu&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;Will:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;Parrot CodeString performance improvements&lt;/li&gt;&lt;li&gt;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&lt;/li&gt;&lt;li&gt;Parrot makefile deps cleanup&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;/summary&gt;</description>
    </item>
    <item>
      <pubDate>Mon, 10 May 2010 06:11:34 GMT</pubDate>
      <title>Perl 6 Design Minutes for 05 May 2010</title>
      <link>http://www.advogato.org/person/chromatic/diary.html?start=475</link>
      <guid>http://use.perl.org/~chromatic/journal/40351?from=rss</guid>
      <description>&lt;p&gt;The Perl 6 design team met by phone on 05 May 2010.  Larry, Allison, Patrick, Will, and chromatic attended.&lt;/p&gt;&lt;p&gt; &lt;strong&gt;Larry:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;various spec updates, some major&lt;/li&gt;&lt;li&gt;removed &lt;code&gt;p5=&amp;gt;&lt;/code&gt; description because it's not supported in core&lt;/li&gt;&lt;li&gt;deleted &lt;code&gt;self:sort&lt;/code&gt; construct because self isn't a real syntactic category&lt;/li&gt;&lt;li&gt;explained Perl patterns in terms of PEGs, and spec'ed tiebreaking rules explicitly&lt;/li&gt;&lt;li&gt;last but not least, finally purveyed the long-threatened revamp of proto to keep routine and method semantics similar&lt;/li&gt;&lt;li&gt;they all now work much more like the multiple dispatch semantics currently used by STD, where we always call the proto first&lt;/li&gt;&lt;li&gt;the proto is then always in charge of the actual multiple dispatch; it can of course delegate that&lt;/li&gt;&lt;li&gt;and the default for a null body corresponds closely to current semantics&lt;/li&gt;&lt;li&gt;in hacking news, the lexer generator mislaid any alternative that was a bare&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;.&lt;/code&gt; pattern, so cursor_fate never called its alternative, oops&lt;/li&gt;&lt;li&gt;took me a long time to run that one down, because it resulted in a horrendous backtrack causing mysterious misplaced errors&lt;/li&gt;&lt;li&gt;revamped character class parsing to be more helpful and correct&lt;/li&gt;&lt;li&gt;STD now check a normal regex bracket's innards for old-school character class, and warns if found&lt;/li&gt;&lt;li&gt;added a&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;.looks_like_cclass&lt;/code&gt; method to Cursor to detect most accidental uses of P5 ranges&lt;/li&gt;&lt;li&gt;some valid P6 brackets will complain, but the workarounds are easy&lt;/li&gt;&lt;li&gt;just put whitespace on both ends is one way&lt;/li&gt;&lt;li&gt;removed a few of these old-school-ish character classes from STD&lt;/li&gt;&lt;li&gt;changed&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;:tr&lt;/code&gt; language to&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;:cc&lt;/code&gt; language since character classes share it&lt;/li&gt;&lt;li&gt;(translation pays more attention to ordering, but the language is the same)&lt;/li&gt;&lt;li&gt;turned out parsing character classes discovered issues in STD; various character classes needed to backslash &lt;code&gt;#&lt;/code&gt; that would otherwise be a comment&lt;/li&gt;&lt;li&gt;to that end, we now allow &lt;code&gt;\#&lt;/code&gt; in character classes instead of misparsing as unspace&lt;/li&gt;&lt;li&gt;if we find an invalid &lt;code&gt;-&lt;/code&gt; in a regex, we now presume we're in an old-school character class and fail with a sorry instead of a panic to give the character class code a shot at it&lt;/li&gt;&lt;li&gt;STD now uses &lt;code&gt;~&lt;/code&gt; syntax for regex brackets to set &lt;code&gt;$*GOAL&lt;/code&gt; correctly&lt;/li&gt;&lt;li&gt;cleaned up recursive panic detection; it was possible to get both false positives and negatives before&lt;/li&gt;&lt;li&gt;STD shouldn't use 'note' to emit a panic inside a suppose because that leaks the message that should be trapped&lt;/li&gt;&lt;li&gt;STD now suppresses duplicate &lt;code&gt;sorry&lt;/code&gt; messages more correctly&lt;/li&gt;&lt;li&gt; &lt;code&gt;sorry&lt;/code&gt; no longer uses &lt;code&gt;panic&lt;/code&gt; in a supposition, but dies directly to throw the exception to the suppose's try block&lt;/li&gt;&lt;li&gt;STD now allows subscripts on regex variables so &lt;code&gt;$x[0]&lt;/code&gt; isn't taken as a character class; still needs speccing&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;Patrick:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;can we make them consistent?&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;Larry:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;historically S05 has allowed bare arrays to mean interpolation&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;Patrick:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;we've never had a working implementation of that&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;Larry:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;a bare &lt;code&gt;@&lt;/code&gt; would be illegal&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;Patrick:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;it's currently illegal&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;Larry:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;you'd have to backslash it to match part of an email address&lt;/li&gt;&lt;li&gt;it's not like the &lt;code&gt;@&lt;/code&gt; alternations are a big deal one way or another&lt;/li&gt;&lt;li&gt;that'd be a little more consistent&lt;/li&gt;&lt;li&gt;I forced it to think of the sigil as &lt;code&gt;$&lt;/code&gt; than what it really is&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;Patrick:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;after seeing how Jonathan et all did interpolation for quoted strings, I thought we should do the same thing in regexes&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;Larry:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;STD now has a partial fix to prevent leakage of&lt;nobr&gt; &lt;wbr&gt;&lt;/nobr&gt;&lt;code&gt;::T&lt;/code&gt; from role signatures&lt;/li&gt;&lt;li&gt;unfortunately, the current fix will lose signatures of file-scoped generic roles&lt;/li&gt;&lt;li&gt;this probably has to do with not knowing whether we're really going to want a new pad; unfortunately we'd have to look ahead to know that currently&lt;/li&gt;&lt;li&gt;various other minor tweaks and bug fixes in STD and Cursor&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;Patrick:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;mostly responding to messages and reports&lt;/li&gt;&lt;li&gt;should be able to get back to coding full-time and online for the next week&lt;/li&gt;&lt;li&gt;plan to resolve the list and closure issues with NQP and Rakudo&lt;/li&gt;&lt;li&gt;will answer other questions and try to keep other people productive&lt;/li&gt;&lt;li&gt;planning for the Rakudo Star release on June&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;Allison:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;busy with the last week of classes&lt;/li&gt;&lt;li&gt;spent most of it writing a little language with PCT&lt;/li&gt;&lt;li&gt;it was easy to use and easy to swap the stages of PCT&lt;/li&gt;&lt;li&gt;I remembered what Patrick did with LOLCODE&lt;/li&gt;&lt;li&gt;also had a discussion of source code control systems&lt;/li&gt;&lt;li&gt;next week should be more productive&lt;/li&gt;&lt;li&gt;need to work more closely with Debian packagers to get packages into Debian&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;Will:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;cleaning out as many deprecations in Parrot as possible&lt;/li&gt;&lt;li&gt;trying to improve the speed of CodeString after the immutable STRINGs merge&lt;/li&gt;&lt;li&gt;bundling lots of little concats helps&lt;/li&gt;&lt;li&gt;hope to merge in an optimization branch for that by the weekend&lt;/li&gt;&lt;li&gt;want to make that faster or less memory intensive&lt;/li&gt;&lt;li&gt;may require the use of a new StringBuilder for Parrot&lt;/li&gt;&lt;li&gt;hopefully will result in a faster Rakudo build&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;Patrick:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;I've never seen CodeString take a long time&lt;/li&gt;&lt;li&gt;unless you run into memory problems&lt;/li&gt;&lt;li&gt;&lt;p&gt;

* discussion of the StringBuilder PMC *&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;p&gt; &lt;strong&gt;c:&lt;/strong&gt; &lt;/p&gt;&lt;ul&gt;
&lt;li&gt;still working on optimizations, particularly CodeString&lt;/li&gt;&lt;li&gt;looking at more PBC and PBC-building optimizations&lt;/li&gt;&lt;li&gt;PBC size went down dramatically and startup improved for Rakudo&lt;/li&gt;&lt;li&gt;should have that much faster for the 2.4 release&lt;/li&gt;&lt;li&gt;will poke at GC tasks starting next week&lt;/li&gt;&lt;/ul&gt;</description>
    </item>
    <item>
      <pubDate>Sun, 2 May 2010 01:07:12 GMT</pubDate>
      <title>Perl 6 Design Minutes for 28 April 2010</title>
      <link>http://www.advogato.org/person/chromatic/diary.html?start=474</link>
      <guid>http://use.perl.org/~chromatic/journal/40338?from=rss</guid>
      <description>&lt;summary type="xhtml"&gt;&lt;div xmlns="http://www.w3.org/1999/xhtml"&gt;&lt;p&gt;The Perl 6 design team met by phone on 28 April 2010.  Larry, Allison,
Jerry, Will, and chromatic attended.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Larry:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;caught up on a week's worth of backlog&lt;/li&gt;&lt;li&gt;made a few spec tweaks&lt;/li&gt;&lt;li&gt;discussed them with other people&lt;/li&gt;&lt;li&gt;trying to make error messages more awesome in STD&lt;/li&gt;&lt;li&gt;working on the ability to parse the insides of character classes&lt;/li&gt;&lt;li&gt;STD doesn't like parsing itself recursively there&lt;/li&gt;&lt;li&gt;need to iron out a few things&lt;/li&gt;&lt;li&gt;enum names can now be variables&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;Allison:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;Debian packages ready to ship to Debian sponsors&lt;/li&gt;&lt;li&gt;putting together a list of GC tasks&lt;/li&gt;&lt;li&gt;cleaned out the existing page, have the big things listed&lt;/li&gt;&lt;li&gt;trying to decide which tasks to do first&lt;/li&gt;&lt;li&gt;doing a lot of reading and research&lt;/li&gt;&lt;li&gt;my little language project is due on Monday&lt;/li&gt;&lt;li&gt;HLLCompiler was enormously useful&lt;/li&gt;&lt;li&gt;will start working on the GC stuff next week&lt;/li&gt;&lt;li&gt;should also start a fresh pass through the ticket queue&lt;/li&gt;&lt;li&gt;added a workaround for the final remaining TT #389 bug&lt;/li&gt;&lt;li&gt;Jonathan had a test case&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;Will:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;tried to focus on getting Rakudo blockers removed&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;c:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;spent some time getting Rakudo to work with trunk&lt;/li&gt;&lt;li&gt;will need a Rakudo guts hacker for the last part&lt;/li&gt;&lt;li&gt;worked on the compact_string revamp branch with Vasily&lt;/li&gt;&lt;li&gt;merged now&lt;/li&gt;&lt;li&gt;that makes trunk about 12% faster than the 2.3.0 release&lt;/li&gt;&lt;li&gt;will work on a few Rakudo profiles once it works with trunk again&lt;/li&gt;&lt;li&gt;expect at least a 5% performance improvement there&lt;/li&gt;&lt;li&gt;have some other ideas, but won't do them without profiling first&lt;/li&gt;&lt;li&gt;came up with a scheme to reduce PBC size by coalescing strings&lt;/li&gt;&lt;li&gt;Peter Lobsinger is exploring that&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;/summary&gt;</description>
    </item>
  </channel>
</rss>
