Update: Corrected and simplified.

Based upon the single example you've provided this will need modifications, but it might give you a starting point. The basic assumption it makes are that functions in your java code always end with a single '}' in the first column of an otherwise blank line. It uses that to read the file one function at a time and performs the modifications.

As coded, the regex is pretty sensetive to variations in the formating of the source code. This can be loosened as appropriate, but increases the risk of false substitutions. It attempts to retain the original indentation, but it may not work in all situations.

#! perl -slw use strict; $/ = "\n}\n"; while( <DATA> ) { s[ ( nodeName.equals \( \s* " ( [^"]+ ) " ( .+? ) #" new \s+ ( Integer | Double ) \( .+? \)\)\); ) ][msg.isSetField(${2}.FIELD${3}(msg.get$4(${2}.FIELD));]sgx; print; } __DATA__ public Product getProduct(Node node) { // --- bunch of logic here --- if (nodeName.equals("ItemNum")) { product.setItemNumber( new Integer(StringUtils.parseInt(nodeValue, 0))); } if (nodeName.equals("AvgPrice")) { product.setAveragePrice( new Double(StringUtils.parseDouble(nodeValue, 0.0))); } } public Product getProduct(Node node) { // --- bunch of logic here --- if (nodeName.equals("ItemNum")) { product.setItemNumber( new Integer(StringUtils.parseInt(nodeValue, 0))); } if (nodeName.equals("AvgPrice")) { product.setAveragePrice( new Double(StringUtils.parseDouble(nodeValue, 0.0))); } } public Product getProduct(Node node) { // --- bunch of logic here --- if (nodeName.equals("ItemNum")) { product.setItemNumber( new Integer(StringUtils.parseInt(nodeValue, 0))); } if (nodeName.equals("AvgPrice")) { product.setAveragePrice( new Double(StringUtils.parseDouble(nodeValue, 0.0))); } }

Outputs:

C:\test>junk1 public Product getProduct(Node node) { // --- bunch of logic here --- if ( msg.isSetField(ItemNum.FIELD)) { product.setItemNumber( (msg.getInteger(ItemNum.FIELD)); } if ( msg.isSetField(AvgPrice.FIELD)) { product.setAveragePrice( (msg.getDouble(AvgPrice.FIELD)); } } public Product getProduct(Node node) { // --- bunch of logic here --- if ( msg.isSetField(ItemNum.FIELD)) { product.setItemNumber( (msg.getInteger(ItemNum.FIELD)); } if ( msg.isSetField(AvgPrice.FIELD)) { product.setAveragePrice( (msg.getDouble(AvgPrice.FIELD)); } } public Product getProduct(Node node) { // --- bunch of logic here --- if ( msg.isSetField(ItemNum.FIELD)) { product.setItemNumber( (msg.getInteger(ItemNum.FIELD)); } if ( msg.isSetField(AvgPrice.FIELD)) { product.setAveragePrice( (msg.getDouble(AvgPrice.FIELD)); } }

Which is just 3 repetitions of the one example.

I'm not sure I would bother to code a filter for a single 2000 line sourcefile. I could almost certainly do that much more quickly in my editor with a macro or two--or even manually--but its fun to try :)


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re: How to match and transform a multiline pattern? by BrowserUk
in thread How to match and transform a multiline pattern? by nbhatia

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.