comment on

But the idea is to make this as extensible and manageable as possible since there can be new data sources, change in specification or new specification, and change in output format. Any suggestions are most welcome. thank you, Sam

My comments are this:

I think it is best to abstract from something that is working, rather than create something which is abstractly satisfying that you need to get practical results from. In other words, I would just get some sources parsed and then allow the patterns to show themselves and then abstract that into a framework as a framework is needed. Also, I hope that a friend of mine can dig up the link to a CPAN data processing framework that I once saw.. the only only one I found via google was Data::Consumer
There are several modules for parsing fixed with (fixed-length) data:

In reply to Re: framework for data parsing by metaperl
in thread framework for data parsing by sam700

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks