Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

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.

In reply to Re^2: Self Testing Modules by Sheol
in thread Self Testing Modules by Sheol

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (3)
As of 2021-06-21 01:38 GMT
Find Nodes?
    Voting Booth?
    What does the "s" stand for in "perls"? (Whence perls)

    Results (97 votes). Check out past polls.