Front page | perl.perl5.porters |
Postings from September 2014
On 3 September 2014 12:11, sawyer x <xsawyerx@gmail.com> wrote: > On Wed, Sep 3, 2014 at 3:26 AM, Peter Martini <petercmartini@gmail.com> > wrote: >> >> > On Sep 2, 2014, at 21:13, Aristotle Pagaltzis <pagaltzis@gmx.de> wrote >> > >> > It could be good to more consciously curate the one we have, though. >> > Say for example, interviewing people who commit code to ask what their >> > personal unpublished TODO lists contain, and compiling and editing the >> > result; see if there are things in there that could be delegated. >> > >> > Well volunteered? :-) >> > >> >> Replying from phone, so apologies if this is mangled. I'm volunteering >> for this if no one else is interested; I offered up my own todo list as a >> lightning talk at yapcna for precisely this purpose, though so far haven't >> gotten to basically anything on it. > > > > I volunteer to help with it. I don't think I will do a good job alone at it, > but if someone (Peter) is on it, I'll be more than happy to help! In the interest of science, here's my personal vague old TODO list, by topic, but in no particular order: 1. making Perl more suitable for large projects (predictable, less hackish, less dependent on action at distance) 1.1. finish and merge rgs/nomagicopen (the <<>> operator) 1.2. Write a good test suite for overload.pm 1.3. Write a comprehensive test suite for autovivification for every primitive 1.4. look again at lexical $_ out of desperation 1.5. don't make pack return utf8 when it shouldn't 2. making Perl faster 2.1. look again at the ?-> operator or whatever its spelling was bikeshedded to 2.2. look again at having more builtins in a core namespace, like scalar::reftype() (aka the mauve project) 3. Controversial Candy 3.1. pointy blocks, like in Perl 6 (mostly) to create anon closures with named parameters (instead of $_) 3.2. list assignment with holes to get last elements of an array: my ($a, $b, ..., $z) = @foo;Thread Previous | Thread Next