|Problems? Is your data what you think it is?|
Thank you for your prompt response. I think that is what I want.
To learn more about this "caller" would I just be fine with a `perldoc -f caller` followed by a `perldoc -q caller` or is there another section of perldoc I should check as well or instead?
I missed the second part
As per using the building debuging suite, if I am thinking of what you are thinking of, that kind of won't really work. You're talking about `perl -c` and `perl -d` right? That really won't work in my case. Generally I've found those features really useful when the program is meant to run and stay running.
However for some of what I plan on doing, will require a request response model. So the script will be run in many instances where it is easier just have trip alarms at certain points while working on it.
This may sound like it contradicts what I am going for here, as to use caller, I'll need some fake data. However the module using it will be fairly simple. Only really done to keep things tidy and clean/easy to read for moshes.
For what I am planning, I find it would be easier to do it this way, and I am still not a wizard with the debugging suite yet.
However this train of thought brings up another thing I have been thinking over a few days.