use PPR; use Modern::Perl; use Data::Dumper; use Config::General; use Sub::Signatures; my $conf = Config::General->new( -ConfigFile => "pm5.ini", -Plug => { post_parse_value => sub ($name, $value) { $value = split_array_str( $value ) if looks_like_array( $value ) ; return 1, $name, $value; } } ); #naive implementation, excercise for the reader to improve #PPR might be useful to parse this, assuming Perl syntax for the #array sub split_array_str ($value) { return [split ",", substr($value, 1, -1)]; } #naive implementation, excercise for the reader to improve sub looks_like_array ($value) { return $value =~ m#^\[# && $value =~ m#\]$#; } my %conf = $conf->getall; print Dumper( \%conf );


holli

You can lead your users to water, but alas, you cannot drown them.

In reply to Re: Config::General to read both scalars and arrays by holli
in thread Config::General to read both scalars and arrays by The_Marshall

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.