Whoa! Deja vu! Where'd Matt go?
Don't worry, Matt's still writing summaries. As you may have noticed, Matt's been writing summaries every two weeks. Now so am I. Because we love you, we've decided to arrange things so I write summaries in the weeks when Matt doesn't. We could do it the other way, but that some could see as self-defeating. Heck, when I say "some" I probably mean "all."
So bear with me while I remember how to type all those accented characters and get back into the swing of writing these things (and of reading everything in the mailing lists once more--someone should write a summary for us summarizers).
I'll be sticking to my old "lists in alphabetical order" scheme of writing summaries. Let's get going.
This Week in perl6-compiler
Lev Selector asked for confirmation that Pugs didn't support compound data
@ar.last. Autrijus and
others confirmed that they didn't then, but they do now.
Darren Duncan pointed out that while last week's summary had claimed he was working on implementing MakeMaker in Perl 6, this is, sadly, not the case. He reckoned he'd possibly look into it again when he had tuits and Pugs was more complete (supporting objects, for instance).
Roie Marianer pointed out what looks like some weirdness in Pugs' parsing of lexically scoped subroutines. Warnock applies.
John Macdonald asked for people who wanted to come to the YAPC::NA Pugs hackathon to get in touch with him beforehand, as there is limited space. If you're interested, drop him a line.
Andrew Savige noticed some weirdness in Pugs's slicing behavior. He posted some example code showing the problem. Autrijus agreed that there was a problem and explained that he was in the process of rewriting all the variable types, symbol tables, and casting rules to agree with the Perl 5 model as described in perltie.pod. The rewrite is currently failing tests, so he posted a patch for people who want to play. On Sunday, he bit the bullet and committed the entire 2500-line patch which "touches pretty much all evaluator code."
Meanwhile, in perl6-internals
William Coleda has been trying to add Unicode support to his Tcl implementation and he fell across issues with missing methods in charset/unicode.h. Leo waved a magic wand and checked in an implementation that he fenced around with disclaimers.
Nicholas Clark confessed that Ponie had stalled for some time, but sweetened the pill by announcing that it's about to restart and that he will be able to allocate at least one day a week to the project. He pointed people at the Ponie intro/roadmap that breaks down the required tasks between here and a first release, complete with time estimates. If you're interested in getting Ponie to a ridable state, this is a good place to start.
People were pleased.
Chip donned his "Fearless Leader" hat and announced that Parrot will move to
a monthly release schedule (with an initial three-week "month" to get things
into sync). There was some debate about whether Solaris/SPARC should be one of
the officially required monthly release platforms (Darwin,
win32-ms-cl were Chip's initial blessed three). This morphed into a discussion
of Tinderbox; apparently there are cool things happening behind the scenes.
What do you know? You go away for n months and when you come back people are still talking about calling conventions.
William Coleda announced that he was starting work on removing the core's
Perl* PMCs in favor of using language-agnostic PMCs
internally and loading the Perl ones dynamically as required. He dealt with
PerlArray quickly and the list discussed names and
ways forward with that tricky case. It looks like someone with tuits needs to
add and write tests for some
vtable methods for
Another discussion that wouldn't go away back when I was last writing summaries has come to a head. Parrot's finally migrating from CVS to Subversion. By the time you read this, Parrot's main repository should be at svn.perl.org/parrot. Hurrah!
There were, of course, wrinkles to iron out.
Matt Diephouse wondered if, now that IMCC has been integrated with Parrot, we really need the imcc/ subdirectory. He suggested that maybe its contents should be distributed about the rest of the Parrot directory structure. MrJoltCola (Melvin Smith?) thought it was best kept separate and thought of as a front end. Bernhard Schmalhofer pointed out PAST, another Parrot front end, and suggested that it may make sense to refactor imcc/main.c into (he suggests) src/main.c and imcc/frontend.c, which would make the distinction rather clearer and provide an opportunity to clean up the exported symbols. Leo pretty much agreed with Melvin (no comment on Bernhard's suggestions yet, though).
Leo looked for volunteers to rejig t/src/manifest.t to use .svn/Entries instead of CVS/Entries when checking the MANIFEST. Michael Schwern (possibly accidentally) volunteered.
Meanwhile, in perl6-language
A quick note about notation: I've started borrowing notation from
Ruby/Smalltalk to discuss methods. Where I write
then I am referring to an instance method of
SomeClass and where I
SomeClass.method, I am referring to a class method.
By heck, but I've not been keeping up.
I started understanding what was going on when people started talking about
implicit dereferencing of long chains of references. Larry's saying that even
$foo is a reference to a reference to a reference to a ... to
$$foo will chase all the way along the reference chain
and evaluate to "10." The general response seemed to be, "Wah! How do I make it
not do that?"
Ovid wondered if
According to Luke, it should default to the current topic.
Wolverian's been looking at the Perl 5 debugger and wondered if it would be
possible to add an
eval method to objects that represent scopes.
The idea is that:
$scope.eval 'say $foo'
say $foo with all of
bindings, etc. in place. (I wonder what
$scope.eval 'return' would
do.) At least, that's what I think he meant. Others asked for
clarification. Wolverian also wanted to know how to get hold of a scope's
continuation (or at least the current continuation). Larry has in the past said
that he wouldn't expose continuations in the core language. Others have noted
that it wouldn't be beyond the bounds of possibility to write a Parrot-level
module which would expose them, though.
Stevan Little had some questions about the behavior of the
method. Luke came through with the answer ("when all else fails, consider the
pair to be a one-element hash").
Prompted by a suggestion from Tim Bunce, Ovid started porting the examples in the Perl Cookbook into idiomatic Perl 6. He asked for comments and suggestions on how to proceed.
Marcus Adair proposed, and Luke Palmer strongly seconded, moving the development of the code onto a mediawiki (wikipedia)-style Wiki that has good support for "offline" discussion of code as it develops. Autrijus reckoned that his current practice of handing out SVN committer bits to anyone who expressed an interest and leaving discussion in the files themselves seems to be working pretty well so far. He pointed at pugs.kwiki.org, though.
Bryan Ingerson posted a preliminary cut of Synopsis 26 and asked for comments. Yuval Kogman pointed out that the docs/ subdirectory of the Pugs distribution is filled with documentation that needed proofreading and nitpicking. Go to it, people.
Ovid wondered what:
($x,$y) := ($y, $x)
Juerd reckoned the answer is straightforward, and I must say I agree with him.
Marcus Adair argued that it seems natural that
when used in a list context, should return a list of the Unicode chars in the
string. Opinion seemed to favor the idea, but there's been no ruling from
Larry (or anyone else on the Design Team).
David Vergin wondered if Perl 6 would have an equivalent of
English, which will give sensible names to the various magic globals
(those that still exist, least). The answer: yes and no. There will be no
English.pm module, but the magic globals will all have English names
Marcus Adair wondered about the use of Heredocs as positional parameters.
Luke confirmed that they should work just like they do in Perl 5, modulo minor
matters of spelling (now
qq::to/END/, etc.) and whitespace
Luke pointed out that:
my @a = (1,2,3,4); my @b = @a[1...]; say +@b;
is potentially problematic (he argues it should print "3", but Perl 5 semantics imply that it should print "Inf"). He proposed breaking with the Perl 5 way. Autrijus agreed with him and has implemented his proposal in Pugs.
Coo--That Was Fun, I Think I'll Do It Again Some Time
If you find these summaries useful or enjoyable, please consider contributing to the Perl Foundation to help support the development of Perl.
That's quite enough shameless self-promotion. See you in two weeks.