| [reply] |
| [reply] |
By the blue-coded structure I presume you are referring to a part of the perl syntax that your editor is colouring blue. Seeing as I don't know what editor you are using, or how you have configured it, I don't know what sort of syntax you are referring to.
I have found in the past that if I want to understand the flow of a large perl script that I have not seen before, a good way is often to to run it under the Devel::NYTProf profiler. The report it generates will contain loads of performance information which you can ignore for now, but it will also tell you for each function what other functions called it, and how often, so by reading the report you can get an idea about the flow of the program, and which parts are important, you can also get a clue where the dead code is, as it will not have any calls to it. (Though make sure you allow for error handling code before you remove anything.)
| [reply] |
You might want to take a look at Padre, which is a IDE built specifically for Perl. | [reply] |
Is there a way I can just pull out certain bits and pieces of the program - say just the blue-coded structure, and not the variables.
Well, you can configure your editor so any non-blue colour is the same colour as your background colour. Or you write your own parser (or modify an existing one)...
Another related question is are you aware of some tool that would take the any perl program and enable me to view the program as a flowchart to see how it has been written and learn from it?
Flowcarts? Sorry, Perl didn't exist in the '70s.
| [reply] |