this code is doing many things ... couldnt debug what mistake i am doing
These two statements are not unrelated. There are various aspects of your code as it stands which will hinder debugging. The main one is that it is monolithic - if you were to split out the various parts into subs it would help to isolate problems and allow for simpler testing.
Other potential pitfalls include:
- Inconsistent indenting. perltidy is an obvious tool to help with that.
- Lack of fault tolerance. eg. calling chdir without checking to see whether or not it has succeeded. Consider autodie as a first-order fix.
- Lack of meaningful comments. Some lines of code commented out with no explanation as to why.
- Variables assigned to which are never read (eg. $filesynth). perlcritic can pick up such situations.
Writing quality code isn't easy but having put the effort in (even just using the tools I've mentioned) it does make debugging, testing and maintenance so much easier.
Good luck with your ongoing debugging.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.