The nested modifier, while it may have already been rejected, could have some tidy little uses.

s/foo/bar/ for (@these) if ($this);
[download]

I suppose that could be accomplished as

map { s/foo/bar/ } @these if ($this);
[download]

but is that as clear as the first statement? Using map in void context to get the effect of a for seems clumsy.

As for something I'd really like to see, interpolation of method calls in a string.

print "The 'bar' attribute of object 'foo' is $foo->bar();\n";
[download]

As it is, I get to do the oh-so-readable

print "The 'bar' attribute of object 'foo' is @{[ $foo->bar() ]};\n";
[download]

That doesn't look like it should work, but it does.

While I'm on the concept of OOP, I think I'd like to see Perl actually implement some form of strong encapsulation for objects "out of the box" as opposed to having to roll your own or re-use your "tried and true" method, whatever that may be (CPAN or home-grown).

Certainly the "defined or" (dor) functionality would be a serious benefit to prevent warnings in my code.

That's about all I can think of at this late hour. Time to sleep.

---

---

• 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.