When someone makes claims that something is a "problem", particularly when they start waving the magic word "solution", it's sometimes insightful to replace "problem" with "possible issue" and then ask:
- What evidence has been provided that this is a real issue?
- What is the nature of the issue? Who does it affect, how, and when? Is it likely to affect me?
- How is the issue mitigated?
- Is the cost of the mitigation worth the effort?
In the specific case the visibility of member variables (hash elements) of stock Perl objects, yes, they are visible. Is this a problem? It comes down to a matter of trust. If you trust yourself and your team to not abuse the feature, I'll argue, (based on experience with two substantial perl-based applications, one in the 600KLOC range) that visibility isn't an issue worth the cost of the various workarounds.
If you don't trust your team, then visibility is an issue, but isn't your biggest issue.
YMMV.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.