Erm ... why???

I mean, configs are in general small and loaded just once so the time spent loading and parsing the data is 1. negligible and 2. mainly the time it takes to read the data from the hard drive/network if it's not already in cache. It might make some tiny sense to measure the access to the already read data, but the loading itself is best left outside the benchmark.

I do believe the choice of the config reader should depend only on the format of the config file and the API it provides. Anything else is a premature microoptimization which is as we all know the root of all evil.

Jenda
Enoch was right!
Enjoy the last years of Rome.

In reply to Re: RFC: config::simple vs config::ini by Jenda
in thread RFC: config::simple vs config::ini by thanos1983

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.