For starters, don't use 'b' for a module name. In Windows, it conflicts with the B:: hierarchy.
Wrap the sub import in a BEGIN and move it above the use, as shown below. You're suffering the same problem as Undefined subroutine errors.
##### aa.pm ##### package aa; sub import { print "import in $_[0] called from ". (caller(1))[3] ." \n"; } use bb; # ... 1; ##### bb.pm ##### package bb; sub import { print "import in $_[0] called from ". (caller(1))[3] ." \n"; } use aa; # ... 1; ################# >perl -e "use aa; use bb;" import in aa called from bb::BEGIN import in bb called from aa::BEGIN import in aa called from main::BEGIN import in bb called from main::BEGIN
Circular inclusions are almost always caused by bad design. The above is simply a workaround.
Update: It turns out the BEGIN is not necessary, but the use must follow sub import.
In reply to Re: Circular use doesn't call import() as expected...?
by ikegami
in thread Circular use doesn't call import() as expected...?
by asokoloski
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |