develooper Front page | perl.perl5.porters | Postings from January 2022

Re: Broken stack traces from use statements.

Thread Previous | Thread Next
From:
Leon Timmermans
Date:
January 14, 2022 14:54
Subject:
Re: Broken stack traces from use statements.
Message ID:
CAHhgV8iL7KbPxGZA4bnjB+KH1xEkdXP+TN_fciP9fgOCAS1Tpw@mail.gmail.com
On Fri, Jan 14, 2022 at 3:33 PM demerphq <demerphq@gmail.com> wrote:

> What breaks is a test that checks what modules are loaded by DBIx::Class.
>> The change in behavior causes it to make different conclusions as to who is
>> loading what. I suspect this is representative for the sort of code that
>> would be affected by this change.
>>
>
> But those assumptions are basically broken, so I'm not sure your point.
> Classic case of GIGO.
>

It's not broken if it gets the job done, is it?

I agree with you that the new behavior is far more usable than the older
behavior, but that doesn't mean people haven't put the old behavior to use.

Leon

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About