Re^3: Modules inheritance

That sort of "circular reference" is a fairly common issue. Often breaking circularity involves pulling out some common code B that is used by both A and A::2.

You may get better answers if you can show us a small sample of your code showing the issues.

Probably it's a typo, but "Use A::n" is not valid Perl - Perl is case sensitive; use is lower case.

Premature optimization is the root of all job security

Comment on Re^3: Modules inheritance Select or Download Code

Replies are listed 'Best First'.
Re^4: Modules inheritance by Arsenii Gorkin (Novice) on May 26, 2016 at 22:21 UTC
Yes. It was just an example. (regarding `Use A::n`). Sorry for my rush)) To be honest: I would be so glad to share all my code but it is toooo long (15 modules now and a lot of files calling them). I use always some tricks to go over that issues but now I am done to do that and want to find a really charm idea how to beat that issues)). I am really happy you caught the idea of circularity between packages. This is the very problem. Sometimes it says: cannot locate method "new" via package "blabla::1" or so... It hurts me so much))	[reply] [d/l]

Replies are listed 'Best First'.

Re^4: Modules inheritance
by Arsenii Gorkin (Novice) on May 26, 2016 at 22:21 UTC

Use A::n

To be honest: I would be so glad to share all my code but it is toooo long (15 modules now and a lot of files calling them). I use always some tricks to go over that issues but now I am done to do that and want to find a really charm idea how to beat that issues)).

I am really happy you caught the idea of circularity between packages. This is the very problem.

Sometimes it says: cannot locate method "new" via package "blabla::1" or so... It hurts me so much))

[reply]
[d/l]