in reply to new features in perl5 - who needs it?

Partly because I've got no responses for this proposal on p5p.
Really? Your first post about this subject dates from Feb 13. 6 direct and indirect replies were posted on Feb 14 and 15, trying to figure out how to fit it in with other method/class plans for 5.12. Noone shot it down. For p5p, that counts as a huge success, specially considering it isn't clear how your suggested change changes existing code. You posted a link to a patch four days ago, and now you're getting impatient people didn't instantly embrace and committed your patch? Get real. There are only a few people that will understand the effects of your patch, and those people 1) have a life as well, 2) may actually take some time to form an opinion.

Considering that (mainly due to the tuits required to actually do significant things is concentrated upon a handfule of people) perl5 progresses slowly -- from 5.8 to 5.10 took 5 years; from 5.10.0 to 5.10.1 is taking 14 months and counting -- you shouldn't expect 5.12 to happen any time soon. Just because your post didn't get a reaction in 4 days doesn't mean anything.

And remember, 5.12 will happen. Just not this week.

  • Comment on Re: new features in perl5 - who needs it?

Replies are listed 'Best First'.
Re^2: new features in perl5 - who needs it?
by dk (Chaplain) on Feb 23, 2009 at 12:20 UTC
    No no, the first proposal, I agree, the solution to the original problem was well-accepted, which actually motivated me to look deeper. The patches I've sent, I do NOT want them committed, they are not ripe yet.

    I'm not complaining, really. I'm simply confused because I write extremely rarely to p5p, and I don't know what to expect from there. And honestly, I don't know if there are people like me who still want something new from perl5. If yes, I'll be glad knowing that what I'm planning to do is needed. Don't look for hidden messages in my mail, or you'll find them :)