.prn Files, in concept, are ancient artifacts in lore of computing even predating Unix. There long history leads me to believe that this problem has been solved on the module level already. Premature coding is a problem for the impaitient. A little research and planning go a long way to making code useful.
Remember this problem is one of the fundemental reasons for Perl. Practical Extraction and Report Language is one of the earliest backronyms attached to it (http://en.wikipedia.org/wiki/Perl#Name).
Oh and look at that just moments after you chided me for not coding in a frenzy some one pointed out the other part of the problem has been solved with a CPAN module. Think of all that wasted code.
As it happens I did read the how to post guide and I had searched on PM for anything on PRN files and going back 2 years did not find anything relevent.
I also wrote a title that unambigously defines the problem not the solution. If and when I complete this project and someone else come looking for information on reports, excel convertions, prn files etc. they will look at this subject and say "YES" someone has a similar problem to my own. They will look in the thread and will find some useful answers. Which is one of the objectives of PM.
Someone with your rank in PM, pedigree in Perl and programming in general would have a better response than "Why haven't you started coding already?"
In reply to Re^2: Converting txt Reports (.prn file) in Excel with Perl
by admiraln
in thread Converting txt Reports (.prn file) in Excel with Perl
by admiraln
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |