warnings.pm provides no way to specify the call frame #16257
warnings.pm’s functions, warnings::enabled, warnings::warnif, etc., do not provide sufficiently fine-grained control over which call frame’s bitmask is looked at, which is why DBM::Deep fiddles with the bitmasks itself, and is currently broken with blead.
I would like to propose that every warnings:: function that accepts a $category/$object also take an optional numeric argument following it specifying the precise number of call frames.
That way, DBM::Deep will no longer have to use such brittle code for future perl versions.
In more detail:
perl -V output, which is somewhat irrelevant to this proposal:
Summary of my perl5 (revision 5 version 27 subversion 6) configuration:
Characteristics of this binary (from libperl):
Father Chrysostomos <email@example.com> wrote:
I think it would be better to use new names for the functions taking a
On Mon, 20 Nov 2017 01:56:29 -0800, arc wrote:
I think _at_ would make sense for all four, since the warning will say ‘at xxx line xxx’.
If nobody objects, I will go ahead and implement _at_level versions of these soonish.