I knew I was going to get a response like this. I know PERL's attitude towards enforced privacy and I'd agree that in general its a good approach. However in this situation we really need this data structure read-only. We have had so many hard to trace bugs because developer A changed some variable (sometimes inadvertently) that then screwed developer B. And then finger pointing and hate mongering ensues. The developer who went and made the DS writable was certainly breaking the rules. I was just wondering if there was a way to really enforce the rules this time. And more specifically I was trying to learn some details about the Internals package and what might happen if I start messing with it.

In reply to Re^2: redefining Internals::SvREADONLY by ChiefAl
in thread redefining Internals::SvREADONLY by ChiefAl

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.