Are circular dependencies considered bad design?

Question

In my work (which is 90% Java but I\'m sure this question applies to other languages) I often create two classes that \"know about\" each other. More concretely, class A im

Answer 1

Yes , It's bad design , It's contradicting the oop principles , It's seems you have to create a new class or interface will contain the the shared parameters and function for a and b , a and b imports this new class...