Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

Personally, I'd just grab the file names, line numbers, and function names for the bottom 10 stack frames and do zero formatting. Just stuff those into a simple array. You can format those later only if the information needs to be shown.

You can likely format the information better than Carp does because you know your specifics. For example, I don't want full paths for every single source file at work because most of them are going to start with /site/ourcorp/myproduct/version/lib/FOO, a long value whose repetition just makes it harder to read the useful information.

I also don't want to see the attempts at abbreviating which arguments got passed to each function. If I really need that level of detail, then I'm going to build my own way of declaring "this is what is interesting about this particular call to this function" rather than hoping that an extremely terse summary of the top-level structure of each argument is even moderately informative.

I would hope that such would be less of a performance impact than what Carp does. But I have not measured the difference. It might still be too slow for your case.

- tye        


In reply to Re: lightweight stack info (data > text) by tye
in thread lightweight stack info by hv

Title:
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 How to display code and escape characters are good places to start.
Log In?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others imbibing at the Monastery: (5)
As of 2024-03-28 08:53 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found