I agree on a warning, it would be a practical thing, after all. And after that, a real fix with 'die' a couple versions later should help the legacy code.
Well anyway, I found the code suggested by ikegami, so would you guys review the patch please?
--- pp.c.0 2012-01-06 01:07:34.511988700 +0100
+++ pp.c 2012-01-06 19:04:06.311428300 +0100
@@ -515,9 +515,11 @@
SvTEMP_off(sv);
SvREFCNT_inc_void_NN(sv);
}
- else if (SvPADTMP(sv) && !IS_PADGV(sv))
+ else if (SvPADTMP(sv) && !IS_PADGV(sv)) {
+ Perl_ck_warner(aTHX_ packWARN(WARN_MISC),
+ "Implicit copy of a read-only scalar due to aliasing");
sv = newSVsv(sv);
- else {
+ } else {
SvTEMP_off(sv);
SvREFCNT_inc_void_NN(sv);
}
-
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.
|