That's because in one (or more cases) I do setup-work at BEGIN time, so that any invalid references are caught @compile time. I'm not thinking of 1 particular or specific use case, but several use cases that seem related, but that *could* have different design needs -- so I want to find an orthogonal design that accommodates various usages including ones I may not have thought of yet.

As a simple example of a simple OO usage w/'use'

use Data::Vars [qw(one two three answer)], {one=>1, two=>2, three=>3}; my $p=Data::Vars=>new(); $p->answer=$p->one+$p->two*$p->three; P "answer=%s", $p->answer; answer=7
Will have to think of more situation as I'm getting tired right now...

In reply to Re^2: Design question: storing package 'flags'. by perl-diddler
in thread Design question: storing package 'flags'. by perl-diddler

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.