G'day holli,

This interested me because it seemed to be (sort of) the opposite of what a newline does with Perl5's die. Adding a newline to the message stops additional information such as line number and code source (not actually a stack trace):

$ perl -e 'die "with info"'
with info at -e line 1.
$ perl -e 'die "without info\n"'
without info
$
[download]

However, when I tried that with Perl6, it printed the message (with a newline where added) and the same information regardless of whether a newline had been used:

$ perl6 -e 'die "with info"'
with info
  in block <unit> at -e line 1

$ perl6 -e 'die "without info\n"'
without info

  in block <unit> at -e line 1

$
[download]

Putting the die in a sub, didn't change the Perl5 output:

$ perl -e 'sub dead { die "with info" } dead()'
with info at -e line 1.
$ perl -e 'sub dead { die "without info\n" } dead()'
without info
$
[download]

But, with Perl6, it gave the same information as before, plus info on the sub calling the die, with and without a newline:

$ perl6 -e 'sub dead { die "with info" }; dead()'
with info
  in sub dead at -e line 1
  in block <unit> at -e line 1

$ perl6 -e 'sub dead { die "without info\n" }; dead()'
without info

  in sub dead at -e line 1
  in block <unit> at -e line 1

$
[download]

I tried a further level of calling. The Perl5 output was unchanged. The Perl6 output added the extra level to the stack trace but was otherwise unchanged.

$ perl -e 'sub drop { dead() } sub dead { die "with info" } drop()'
with info at -e line 1.
$ perl -e 'sub drop { dead() } sub dead { die "without info\n" } drop(
+)'
without info
$ perl6 -e 'sub drop { dead() }; sub dead { die "with info" }; drop()'
with info
  in sub dead at -e line 1
  in sub drop at -e line 1
  in block <unit> at -e line 1

$ perl6 -e 'sub drop { dead() }; sub dead { die "without info\n" }; dr
+op()'
without info

  in sub dead at -e line 1
  in sub drop at -e line 1
  in block <unit> at -e line 1

$
[download]

I've tinkered with Perl6 every few years or so, just to see progress, but I'm very much a novice. Please provide some example code and output demonstrating what you're describing; it's entirely possible I've missed the point.

Assuming the version number refers to a date (YYYY.MM), it looks like my copy of Perl6 is about 18 months old: perhaps the behaviour you describe is new.

$ perl6 -v
This is Rakudo version 2016.04 built on MoarVM version 2016.04
implementing Perl 6.c.
[download]

I'm pretty sure the Perl5 behaviour has always been the same (such as I've shown); I certainly recall using it in v5.6. Just for completeness, my current version:

$ perl -v | head -2 | tail -1
This is perl 5, version 26, subversion 0 (v5.26.0) built for darwin-th
+read-multi-2level
[download]

Update (cosmetic): I removed instances of "ken@ganymede: ~/tmp", which are part of my complete prompt, unrelated to anything I posted, and really just noise. I normally take these out before posting; a few had slipped through this time.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.