The discussion started at Getting size of call stack describes a straightforward way to get the current call stack size: 
for ($depth = 0; caller $depth; $depth++) {1}

[download]
(That's my own implementation of the algorithm.)

This is a pretty inefficent way to get the stack depth. For implementations where this is only needed once, e.g. as part of generating a die message, that's not much of an issue. I have a tracing module that produces lots of debugging output, and I'd like to add an indication of the stack depth to each line of debug output -- that would lead to alot of repetition of this loop.

Does anyone know of a more efficient method for finding just the stack depth without using multiple calls to caller() each time you need that number?

--DrWhy

"If God had meant for us to think for ourselves he would have given us brains. Oh, wait..."

In reply to Getting the size of the call stack (efficiently) by DrWhy

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


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.