comment on

> If this is something ignored usually, I will ignore it, but I would like to know how to make it better. Should I just assign $_ to a variable and then use the variable?

This is what I do if $_ is a non-reference scalar. Otherwise, you'd have to take some extra steps to ensure a deep copy of whatever it's referencing. I generally only use map occasionally, and it's always in some sort of a transform operation that doesn't actually modify $_. But that's me.

>Another thing that I am confused by is why the expression form of eval is discouraged?

I don't do that because it means I am getting clever, and we know that leads to needing to have more than clever debugging skills. Again, that's just me, but I've been bitten by this too many times to not believe in the hidden future cost of cleverness. It's also a security vulnerability waiting to happen.

In reply to Re: Perl::Critic says don't modify $_ in list functions and other things by perlfan
in thread Perl::Critic says don't modify $_ in list functions and other things by Lady_Aleena

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.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks