in reply to Re^5: diagnostics: warning, deprecation, error
in thread diagnostics: warning, deprecation, error
You two removed the crucial file and line number.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^7: diagnostics: warning, deprecation, error
by marto (Cardinal) on Feb 17, 2026 at 20:27 UTC | |
This is not the case. On an unmodified perl running perl -MDerp::Derp outputs:
Calling the same way from the patched perl produces the output shown here. From within a script we get the expected result:
| [reply] [d/l] [select] |
|
Re^7: diagnostics: warning, deprecation, error
by pryrt (Abbot) on Feb 17, 2026 at 17:18 UTC | |
Because my experiments say the latter.
I obviously cannot test whether marto's unpublished fix behaves the same way. But just because the example shows a situation in which the line number and file name aren't shown (because they are meaningless) doesn't mean that the solution proposed will actually get rid of that information when it's available.
edit: I see that between the time I started my post and when I actually posted, the AM posted essentially the same information, with confirmation that their suggestion does not get rid of that information. | [reply] [d/l] [select] |
|
Re^7: diagnostics: warning, deprecation, error
by Anonymous Monk on Feb 17, 2026 at 16:42 UTC | |
We did not. My example uses a bogus module on the -M switch to trigger Perl and when done like that she does not return file and line number not even good old at -e line 1. For that you need to run perl from a file:
Can't locate Blorp.pm in @INC you may need to install the Blorp module @INC entries checked: /Users/u/perl5/perlbrew/perls/perl-5.42.0/lib/site_perl/5.42.0/darwin-2level /Users/u/perl5/perlbrew/perls/perl-5.42.0/lib/site_perl/5.42.0 /Users/u/perl5/perlbrew/perls/perl-5.42.0/lib/5.42.0/darwin-2level /Users/u/perl5/perlbrew/perls/perl-5.42.0/lib/5.42.0 at /tmp/blorp.pl line 1. BEGIN failed--compilation aborted at /tmp/blorp.pl line 1. | [reply] [d/l] |