I meant that both of the potential fixes for this feel unnatural:
- using s/(x)/fn "$1"/e (with quotes around $1), or
- using what you suggested: (my $new = $old)... or any other form of that.
Both fixes require an extraordinary amount of coupling between the caller and the function. Either:
- the caller needs to know that the argument to fn() will be used directly from @_ after a regexp, or
- the function needs to know that the argument is an alias of a global variable which will be modified by the regexp.
Only if they have this tight coupling does it make sense to use either of these two precautions to avoid the issue I ran into.
I think the takeaway for me is that when passing $1, etc into a function, that it should be quoted (to copy it), even though the general rule is when passing a variable $var into a function, (almost) never should it be quoted, as in fn("$var"). This feels exactly like the kind of kludgy rules you have to remember to use C++ "correctly".
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! —
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.