Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked

comment on

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

I can reproduce that on Win with 5.032001, but not the magic appearance of your

> 3.1     use feature 'say';

and the followin say statements, which are also not in the source you've shown.

I also looked into @DB::dbline which is aliased to @{"::_<"} to be sure, and there was no "feature say".

Could it be you debugged another file, where you swapped print with say ?

FWIW: Those internal vars are explained in


> but it's pretty surprising that we've had this bug for 32 years!

Frankly, the debugger does so may weirdly elaborated things ...

... I assume most who saw this just thought it's a yet unknown feature to be explored.

Cheers Rolf
(addicted to the 𐍀𐌴𐍂𐌻 Programming Language :)
Wikisyntax for the Monastery

In reply to Re: A Perl 3 bug in the debugger by LanX
in thread A Perl 3 bug in the debugger by pemungkah

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.