On Mon, Jul 17, 2017 at 2:49 AM, Joachim Durchholz via RT < perl6-bugs-follo...@perl.org> wrote:
> 1) It cannot handle non-runtime code that one might want to filter. > 2) It hardcodes the definition of what's interesting. > 3) You cannot have runtime code that you *want* to be included in the > backtrace. > 4) It adds a design constraint about what can go into which module of > the runtime. > 5) The design constraint is nonobvious. > 6) If somebody writes his own module in a different location but with a > matching name (e.g. they might be writing a wrapper, or an emulator), > then these files will be filtered as well. > 7. When Perl 6 gets used on the web, someone *will* find a way to abuse this (e.g. to obscure how they broke into something). -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
