comment on

> That's an overstatement. The only thing that can be impacted is a sub that tries to modify an alias and then gets passed a read-only value and where that situation isn't just declared a bug and gets fixed.

...

> If no error is ever thrown, then nobody knows and nobody cares and there is nothing to fix.

Wrong, as you can see from the code I posted, not only the sub is affected, but the intended side-effect (of altering the call-by-reference argument) is missing without warning.

in continuation of Re^3: ref to read-only alias ... why? (not consistent)

  DB<111> $x=0; for ($x,0) { print; inc_b($_); print " -> $_\n"}
0 -> 1
0 -> 0
[download]

> So, yes, exactly as I said, the worst possible case can be solved by adding a simple eval around the code that modifies the reference

How is eval supposed to help here?

> but is (badly) designed to also tolerate the failure in the case of read-only parameters.

So in your opinion manipulating $_[0] is a bad design!?!

Could you please post some code-examples to illustrate your point of view?

Cheers Rolf

In reply to Re^8: ref to read-only alias ... why? (eval) by LanX
in thread ref to read-only alias ... why? by dk

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.


laziness, impatience, and hubris
	PerlMonks