I second [id://ikegami]'s comments. If anyone outside you module needs to look at or set the value, you should provide methods or functions for them to use. This simplifies not only your immediate problem, but opens an actual API for clever things in the future.
If you had the methods, knowing the name of the module and the name of the method (even if they are in variables) is far preferable to the games needed to make direct access work.
Further (added later), you should probably implement an import method in the bar class. It will receive the caller's name, making it even easier to do whatever it is you are doing.
Phil
Update: Added the part about import.
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.