I once wrote an interface to a low-level API accessing a database. The point was to simplify the access to data by hiding many of the gory details of the low level API. One of the things I did in my interface module was to store in closures most of the information I did not want the module user (usually me) to have to care about (connection ID, transaction ID, error buffer ID, etc.). The user would just need to call an init function at the beginning of the program and then simply call the functions to query the data, the module taking care of the underlying details. I do not know if this applies to your case, but I was quite happy with this solution which made our lives much easier.

In reply to Re: User preference: To store params or not by Laurent_R
in thread User preference: To store params or not by stevieb

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.