Here is what I mean by commified. Consider the following 2 versions of the same map statement:

...map{"@$_\n"}@a...
...map"@$_\n",@a...
[download]

The first form is more general, you can put more complex logic inside the block. The second form replaces the block with a comma and shaves a character. Often you can shave a few characters off of someone's solution by seeing that a few map's or grep's can switch over to the version with the comma.

Sometimes it is not obvious that you can. So sometimes I just have to try it out. As in the case:

...map{$$_[0]>$i?():[$i,@$_]}P($n-$i)...
...map$$_[0]>$i?():[$i,@$_],P($n-$i)...
[download]

Incidentally the following version is the same size, but has slightly nicer (IMHO) output:

sub P{
my$i=pop;[$i],map{--$i;map$$_[0]>$i?():[$i,@$_],P($_-1)}2..$i
}
[download]

---

---

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