I think we can confirm that the fact that $1 leaves this function with the SVf_POK flag on is a bug.
Yes.
demerphq had this to say with regards to why $1 doesn't carry the READONLY flag:
Not a problem for my solution. The setter called via mg_set after the upgrade will throw an error if appropriate.
Turns out that this is deliberate, as some pluggable regex engines allow for a writable $1.
That means that upgrading $1 might have no effect or might upgrade the entire source string in those engines, but I don't see that as a problem. Side-effects are expectedintended when playing with magical variables.
Incidentally, this bug is a regession in Perl 5.10. Perl 5.8.8 doesn't have this problem.
That would explain the presence of sv_utf8_upgrade_nomg.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Outside of code tags, you may need to use entities for some characters:
| |
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.
|
|