Storable is very good but might be more than is needed for this use case.

If the preferences are all numeric and text values then it might be simpler to use a text based config format. That way users can see and edit their config values using a text editor. There is always the risk they will make a mess of the formatting but you could always add big warnings to the top of the file so it is caveat emptor if they do. (Edit: And fall back to system defaults with a warning when that happens.)

See for example Config::Any for a list of options, e.g. YAML, JSON or INI. Best to avoid the Perl format since it is loaded using do {} so will run any code in the file and is thus a potential security issue.

In reply to Re: Storable for user preferences by swl
in thread Storable for user preferences by Bod

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.