Front page | perl.perl5.porters |
Postings from July 2006
> Also, are there any areas in core perl that could be usefully improved, for
> which it is possible to give reliable, bounded estimates of the work
> involved?
>
> Nicholas Clark
This I don't feel like I have any guage on the community, and anticipating what
people will like is difficult (what people think they want and what they actually
want are two very different things -- ask any consultant). But here's an on-the-
spot personal wishlist:
* ByteLoader speed up such that bytecode compiled modules, such as those compiled
with Pugs, dumped with the P5 backend, and then dumped to bytecode, load much
more quickly than parsing P5 from source.
* Coro support in core, including the large scale refactorings needed to make it
clean. Even if Coro isn't core, I'd like to see tree structured stacks so
that it can be cleanly plugged in. In general, anything that makes P5 a more
viable P6 backend, I'm gung ho for.
* What the hell -- clean up OO a bit. Add a 'method' that, if nothing else,
shifts off $self. Put it in $_. Or something. Make a 'has' that does
some Data::Alias-like trickery, such that C<< has $foo >> would do essentially
C<< alias my $foo = $self->{foo} >>, and C<< has @foo >> would do
C<< alias my @foo = @{ $self->{foo} } >>. It's easy to argue that Perl doesn't
need yet-another-OO-hack, but it keeps getting more and more anyway. While I
welcome Perl 6, I'm still planning on spending Chrismas with my family. Good
things could come from P6 syntaxisms with some, but not all, of the P6 semantics.
I was going to go on, but that last one would have me dancing in the streets =)
-scott