Parsing Verilog files can be tricky, and you should probably use a parser: Verilog-Perl. But, this might work for simple files: 
use warnings;
use strict;

# Change input record separator to parse whole Verilog lines
local $/ = ';';
while (<DATA>) {
    s/\s+/ /g;    # Convert all whitespace to single-space
    print "$_\n";
}

__DATA__
 DFFX1 k0_reg_184  ( .D(key_184 ), .CLK(clk), .QN(n18736) );
DFFX1 k0_reg_183  ( .D(key_183 ), .CLK(clk), .Q(k0_183 ), .QN(n65993)
         );

[download]

Output: 

 DFFX1 k0_reg_184 ( .D(key_184 ), .CLK(clk), .QN(n18736) );
 DFFX1 k0_reg_183 ( .D(key_183 ), .CLK(clk), .Q(k0_183 ), .QN(n65993) 
+);

[download]

In reply to Re: File modification on the fly (Verilog) by toolic
in thread File modification on the fly by mavericknik

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.