I'll need help with the following problem. Consider we have a class A, that inherits from class C and uses some syntax sugar as defined in B. Here's A:
package A; use lib '.'; use strict; use warnings; use B qw(moo); use C; use Exporter; our @ISA = qw(C); A-> new; moo; 1;
Here's B:
package B; use strict; use warnings; use Exporter; use vars qw(@ISA @EXPORT_OK); @ISA = qw(Exporter); @EXPORT_OK = qw(moo); sub moo { print "B::moo\n" } 1;
and here's C:
all three in 3 different files, for example. Now, running that code, surprisingly for me, yields "B::moo" twice, whereas I'd expect that first time it would print "C::moo". As you can see, B::moo is being invoked instead of C::moo.package C; use strict; use warnings; sub new { bless({}, shift)-> moo }; sub moo { print "C::moo\n"; } 1;
Now, the question. I understand how it works, but I don't know, if there are any good practices to protect A and C from being abused that way? It's a fairly realistic scenario if A doesn't know that C::moo exists at all, or even worse, doesn't exist today but will exist in a newer version of C. It's not uncommon to have third-party modules to export names, but is there a simple technique to import them in a safer manner?
Thank you!
In reply to Need help with clashing method names by dk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |