So it turns out I was misreading the documentation. When it says "replace your calls to NEXT::method() with maybe::next::method()," it means that literally. I was taking it to mean, for example, that NEXT::new(@_) becomes maybe::next::new(@_), but really, it should become maybe::next::method(@_). I'm still a bit confused about why this is so, but it works, at least.
In reply to Re: Class::C3::Adopt::NEXT warning on deprecated NEXT
by bv
in thread Class::C3::Adopt::NEXT warning on deprecated NEXT
by bv
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |