develooper Front page | perl.perl5.porters | Postings from September 2014

Re: Roadmap/plan for Perl 5?

Thread Previous | Thread Next
Father Chrysostomos
September 3, 2014 13:23
Re: Roadmap/plan for Perl 5?
Message ID:
sawyer x wrote:
> > Basically, todo.pod and the RT system (the latter more than the for-
> > mer) are my to-do list.  Plus any bugs I run into.
> Are these leading to anything specific?
> (and I do apologize if that sounded or was disrespectful in any way)

A perl that does not crash or exhibit erratic behaviour when I'm using
it for things pertaining to Real Life.  I.e., I spend much of the
time squashing little bugs one after the other, and searching for
them, too.

That's probably not what you are looking for, right? :-)

> > And, when I have an itch, I work on bigger things.  My current list of
> > bigger things is something like this:


> > Most of those are either very hard or controversial, so this stuff
> > happens slowly.
> If any of these were formalized into "part of the plan" or "required
> necessities to complete the plan", it would be less controversial, and
> perhaps it would be easier to get help for doing it?

The controversial things are mainly features that have not been dis-
cussed enough, or things that I cannot accomplish because others
disagree with the side effects of my proposed solutions.  (Fixing
line numbers bloats memory usage.  Adding error codes my way, which
is backward-compatible, makes strings 'more complex' [though I

Formalising it into part of a plan does not make the controversial
details go away.  And I prefer to spend time *doing stuff* rather than
discussing things to death.

And this discussion is taking me away from the first item in that
list, and also ticket #122673, both of which I am currently work-
ing on. :-)

As for getting help, *I* want to be the one implementing lvalue refer-
ences. :-)

> What I can identify here that I would put under a plan is:
> * Reduce memory usage.
> * Improve debugging tools (Deparse).
> * Improve Unicode support.
> * Solidify keywords as CORE:: subs.
> * Improve parsing.

The things that you list are already happening, but some very slowly.
 Those are goals that I thought were self-evident.  But I can see that
they might not be for others, and I suppose a list of such self-evi-
dent goals could be useful.

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About