How far do you want to go to limit unauthorized access to the internals? Without even const or public/private stuff like C++, the stated policy is to not provide that kind of compile-time checking but to let everyone play nice. There is always raw pointers and Devel::Peek, if it comes to that.

In general, you need to publish and stick to a well-defined interface. If someone goes around that, then all bets are off.

Personally, I want checking like we get with variables and "use strict". But since that's for my own benifit, not to prevent dirty tricks, it's acceptible to have away around it as long as it's not something that's easily done by accident.

In reply to Re: Re: (When) Should I 'use fields;'? by John M. Dlugosz
in thread (When) Should I 'use fields;'? by traveler

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.