Thanks, I had considered that option, but I'd rather have it not warn because nothing is wrong. Suppressing warnings rather than fixing them rubs me the wrong way. I may end up doing this on the interim, since I'm in a spiral development, and need to get a first prototype out quick, but I feel I need to fix the underlying problem.
In reply to Re^2: Class::C3::Adopt::NEXT warning on deprecated NEXT
by bv
in thread Class::C3::Adopt::NEXT warning on deprecated NEXT
by bv
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |