And if you're using Perl on a Windows OS, as an alternative to
Config::IniFiles I recommend that
you look into Dave Roth's really useful
Win32::AdminMisc module. It includes a ReadINI (and a WriteINI) function that "understands" section dividers, and ignores lines commented out with semi-colons. There's online documentation at
http://www.roth.net/perl/adminmisc/, but here's an example of how it could be used:
foreach my $section (Win32::AdminMisc::ReadINI
('some.ini', '', '')) {
foreach my $key (Win32::AdminMisc::ReadINI
('some.ini', $section, '')) {
my $value = Win32::AdminMisc::ReadINI
('some.ini', $section, $key);
}
}
(Note: if you want to use AdminMisc, either use PPM (if you're using ActiveState), or else use the links at
Roth's site. It's
on CPAN but
http://search.cpan.org for some reason
doesn't return a match.)
Finally, in the book Data Munging in Perl (written by davorg), there's a longish discussion about using the high-powered Parse::RecDescent module for parsing INI files.
-- Frag.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.