Some other options:
- Mixin/Role/Trait. Gives every object that needs it a config method.
- Config factory. This is a singleton itself, but it can hand out configuration objects to whoever requests it.
The mixin is conceptually very simple:
package My::ConfigMixin;
use base qw/ Exporter /;
our @EXPORT = qw/ config /;
sub config {
my $self = shift;
somehow_get_config(@_);
}
Which, when used (a simple
use My::ConfigMixin; will do), gives your object the method
config. Since its first param is your requesting object, you can do all sorts of filtering based on $self (access control, limiting output, etc).
The main issue here is maintaining state. Pretty much your only option is to use package variables in My::ConfigMixin, which can get messy. I'd be interested to learn more about Traits that need state, but sofar I'm a newbie on the subject.
The factory might be a better alternative: it can maintain state on its singleton instance.
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.