comment on

But it's mainly a strike against shoving new features into the language without considering their consequences.

What do you mean by strike?

I've had eew experiences since 5.6, and with every new feature I try I'd always find something that doesn't quite work as documented, or isn't well documented, and I just end up not learning it, and doing things the way I've always done them.

For better and worse, Perl is a mature platform (like ANSI C), and should act it.

What does that mean?

For example a lot of the new regex features are really under documented and under tested, but they're really powerful, and if we waited for more thought/testing/docs they probably wouldn't have been added for another 5 years, even though a lot of them are still considered experimental

I think any new features ought to be experimental for at least 3 releases (5.6,5.8,5.10) and implemented only using Devel::Declare

I'm also in favor of ditching all the warts, if JavaScript can do it ... :)

In reply to Re: Measure twice, cut once by Anonymous Monk
in thread Measure twice, cut once by educated_foo

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Think about Loose Coupling
	PerlMonks