It seems to me that a role would be a far better idea.
Further if the role could check an environment variable, eg.
%*ENV, then it could only stop the default Exception
handler providing backtrace when the environment is set.
May be compiler developers could consider making this part of the
Hi Richard,
I wouldn't call s/// a routine. It's actually (implemented as) a kind of
quote, like Q, q, qq, qw, and also rx, and tr. I consider that an
important distinction, because the syntax with which you call s/// is
very different from how you call a sub. You can't just `say '(' ~ ')'
1234`,
Better implementation idea
A. A role "X-no-trace" to compose into any exception class,
B. which at BEGIN installs into the outermost scope CATCH block for
anything that does X-no-trace,
C. 3-6 as before :-)
that way, no need for COMPOSE block and $?CLASS variable. And as a bonus,
can add the X-no
Richard seems to be close to a workable answer, but now I am wondering
about this issue.
Imagine writing a configuration-checking class (or role) to be sure all the
files and directories exist at startup. The goal is to use exceptions, so
the consumer of the checker can use standard exception hand
