As I read through these points, all I could think of what "what a peculiar collection of features." I daresay my own ideas for extending Perl 5 (keeping Perl 5 Perl 5?) would take it off in another wild tangent. But some of these points seem... worng to me. What a mishmash of ideas. Let's have a look...

1. Dot or arrow? I am getting used to the dot.
   
   
2. Classes. Huh?
   
   
3. on_destroy(). If you need it, you need it bad, I suppose. But the name should be UPPERCASED.
   
   
4. Globs will be replaced by return values. I can't parse that statement in any sensible way.
   
   
5. local has its uses, in terms of overlaying a temporary value on a variable. When you need it, you need it bad.
   
   
6. I have never had a hash mishap with , and/or =>. Again, I don't see the point.
   
   
7. Proper tail recursion. Because it doesn't work correctly at the moment? Maybe so, but as I never use recursion except when playing I don't see this as a burning issue.
   
   
8. Factories. Again, maybe I'm missing something. I suppose I should reread my Gang of Four, but this doesn't do anything for me.
   
   
9. x operator? What, that one must employ the correct use of space? Well ok, but it's not something I lose sleep over.
   
   
10. s/scalar/count/. That's an entirely gratuitous and subjective change.
    
    

hmmm. When you look at it that way, it doesn't seem like such a big deal. Thanks for posting the information. At least I know now I can safely ignore Rindolf :) As far as I can tell, most of these issues are just stylistic, and so the idea is just to bend Perl to be more suited to writing a particular sort of Perl.

<update> And now that I've read the use.perl.org thread I know I can safely dismiss the whole idea as the work of a nutcase. Sorry, but the guy is really off the wall. </update>

As for what directions I'd like to see Perl 5 taking, I wish things like this would work:

• my @arr = @ARGV || (1, 4, 9, 16);
  # || forces scalar context
  [download]

• my @args = ( 'p455w0rD', '5a1T' );
  my $crypt = crypt( @args );
  # crypt is prototyped as sub ($$) crypt;
  [download]

Those are two issues that bit me yesterday (hi japhy!). Although AFAIK these problems are emminently unfixeable because of other constraints.

print@_{sort keys %_},$/if%_=split//,'= & *a?b:e\f/h^h!j+n,o@o;r$s-t%t#u'

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.