Re^2: Optionally / safely disabling a warning category for a complete package (magic numbers)

You're absolutely right that magic numbers are not good, that is a potential weakness of my proposed solutions.

FWIW, when the postderef feature was taken out of experimental status, it was elected to leave the "experimental::postderef" warnings category in place but to make it a no-op. References: commit, P5P

Regards,
-- Hauke D

Comment on Re^2: Optionally / safely disabling a warning category for a complete package (magic numbers)

Replies are listed 'Best First'.
Re^3: Optionally / safely disabling a warning category for a complete package (backward compat) by tye (Sage) on May 18, 2016 at 20:37 UTC
FWIW, when the postderef feature was taken out of experimental status, it was elected to leave the "experimental::postderef" warnings category in place but to make it a no-op. As is good practice and as I would expect. But the next thing I would expect to eventually happen would be to clean out really old cruft by making references to 'experimental::postderef' deprecated and cause a warning and then to later make it fatal (by removing all mention of it from the source code). Not that I'll make any predictions about approximate time frames for such. :) - tye	[reply]

Replies are listed 'Best First'.

Re^3: Optionally / safely disabling a warning category for a complete package (backward compat)
by tye (Sage) on May 18, 2016 at 20:37 UTC

FWIW, when the postderef feature was taken out of experimental status, it was elected to leave the "experimental::postderef" warnings category in place but to make it a no-op.

As is good practice and as I would expect. But the next thing I would expect to eventually happen would be to clean out really old cruft by making references to 'experimental::postderef' deprecated and cause a warning and then to later make it fatal (by removing all mention of it from the source code). Not that I'll make any predictions about approximate time frames for such. :)

- tye

[reply]