Config::Hosts Interface to /etc/hosts file 

if ($hosts->{$ip}) {
  print STDERR "Line $l: Warning: duplicate IP entry $ip, the last one
+ will be used\n";
  }

[download]
As far as i remember(AIX, ubuntu, win) you may have duplicate lines with the same ip and they are "joined".

Also "output" mixes up names and ips in same array. While strange, this is a valid line 
 
127.0.0.1 192.168.0.1

[download]
it makes the host-name 192.168.0.1 map to the ip of 127.0.0.1, common use is by script kiddies tho.

Parse::Hosts Parse /etc/hosts 

    unless (defined $content) {
        open my($fh), "<", "/etc/hosts"
            or return [500, "Can't read /etc/hosts: $!"];
        local $/;
        $content = <$fh>;
    }

[download]
only reads /etc/hosts or you have to read it yourself and pass it in. "output" is an array of hashs {ip => $ip, hosts => \@hosts}

App::ParseHosts Parse /etc/hosts (CLI) Just a wrapper around Parse::Hosts to allow you to read anyfile

Mine parses the lines same way as them, and has more usable data structures for the task and example. Mine doesnt check for valid ipv4 or ipv6 format tho like Config::Hosts almost does. I looked at Config::Hosts first and didnt like it

add: and none are core either

In reply to Re^3: parsing a terrible /etc/hosts by huck
in thread parsing a terrible /etc/hosts by f77coder

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.