comment on

I'm a fan of clean names that avoid confusion. Perl++ would be an accurate description of the intent and draw a direct analog to C++.

How a backwards compatible successor to Perl5 should be named ... no idea. Maybe leaping to 10 like Autocad did?

But I agree that this must be accompanied with clear improvements like signatures (and/or an OO System).

Anything else would be quickly ridiculed as marketing gag.

> that Perl 6 hurt Perl 5 particularly or in the grand scheme.

I claim Osborning, AFAIK Perl5 releases in the 200x years were rare because everybody was expecting Perl6 to arrive. That's a normal psychological effect.

And when Perl6 was officially released I personally witnessed the aftermath of a very strange and loud discussion of my clients to switch as soon as possible to the "newer version".

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery
FootballPerl is like chess, only without the dice}

PS: FWIW: you may want to watch my talk about "The Camel Paradox" (not sure if slides and sound are out of sync or if I was in Muppet mode again ;-)

In reply to Re^12: Ovid's take on the renaming of "Perl6" (updated) by LanX
in thread Ovid's take on the renaming of "Perl6" by 1nickt

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