I still don't see the need to emulate reset (or your buggy code, or why one program does two completely different things), but I understand this has been a looooooooong battle for you. I suggest you read up on some code-refactoring techniques. Some of it is rather obvious, but it may help you try to understand what we are saying and why your antiquated ways need to change. Also read up on error handling, design driven development, and so on. And debugging! If you want to watch values, use a debugger or instrument debugging hooks.
To be constructive, I'll give some feedback. I like to chain GNU tools together, and parse things (running items through sort and grep and such), so I'd do something like the following to keep parsing simple. Shiny output is of little use to machines.
iteration variable value
1 abcdef foo
1 bbcdef bar
2 sheep zebra
or is there hope for my module?
I see little hope. Especially in that you still have a few subroutines and don't even have a module yet. | [reply] |
The text boxes would all be the same size so everything will line up. I could do this with CGI, but I don't know how acceptable that would be for the average programmer.
I thought that it had already been covered that an "Average" programmer would be better suited using localized variables in the first place instead of your rehash of reset.
| [reply] |
corollary -- he's the only one who is going to use this tool, so it doesn't matter what he does with the output.
| [reply] |
Seriously, the best approach to this is to remove your script from PerlMonks, ensure it exists in only one location (say, a 1.44 inch floppy) and then put it out of its misery in a humane fashion (maybe toss it into a river?). To quote a phrase from an ex-housemate of mine - and not wishing to offend any esteemable monks - "you can't polish a turd". | [reply] |
