This is what I would do:

my @devices; open (FILE,"config.txt") or die "cannot open file : $!"; # Always put a label on your loop when using next CONFIG_LOOP: while ( my $line = <FILE> ) { # Never use $_ directly if ( $line =~ /^(\w+)\s+/ ) { # Adding to the array push( @devices, "$1 => " ); } elsif ( $line =~ (/inet\saddr:(\d{1,3})\.(\d{1,3})\.(\d{1,3})\.(\d{1 +,3})/) ) { # Adding the IP address to the last known device $devices[-1] .= "$1.$2.$3.$4\n"; } else { # Skipping other lines next CONFIG_LOOP; } } close (FILE); foreach my $device ( @devices ) { print $device; }
Take my advice. I don't use it anyway.

In reply to Re: need to remove the extra line in regular expression by greengaroo
in thread need to remove the extra line in regular expression by ulaksh

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.