From @masak

<masak> rakudo​: exit
<p6eval> rakudo 18d996​: OUTPUT«␤ in main program body at line 1␤»
* masak submits rakudobug

As far as I understand, &exit, while probably implemented internally
using some exception mechanism or other, shouldn't print a backtrace.
Backtraces are more for when things went wrong.

From @szabgab

use v6;

say 2;
exit;

will gives the following error​:

  in main program body at line 1

and the exit code is 1

The same happens if I call exit(0); or
exit(42);

From @jnthn

On Wed Jun 02 07​:57​:33 2010, masak wrote​:

<masak> rakudo​: exit
<p6eval> rakudo 18d996​: OUTPUT«␤ in main program body at line 1␤»
* masak submits rakudobug

As far as I understand, &exit, while probably implemented internally
using some exception mechanism or other, shouldn't print a backtrace.
Backtraces are more for when things went wrong.

Disappointing backtrace is disappointing.

Fixed now, exit once again exits. Given to moritz++ for spectest.

Thank,

Jonathan

The RT System itself - Status changed from 'new' to 'open'

From @moritz

... and now tested with the awesome Test​::Util (for which I can't give
KyleHa++ too much praise) in t/spec/S29-context/exit.t.

@moritz - Status changed from 'open' to 'resolved'