As i said in the comment, the problem is due to cyclic dependency. In particular, your Student.hpp includes –> Grad.hpp which in turn includes –> Core.hpp which finally includes –> Student.hpp So as you can see from above, you ended up where you started, namely at Student.hpp. This is why it is called cyclic dependency. … Read more
In the headers, forward declare the member functions: class Node { Tree * tree_; int id_; public: Node(Tree * tree, int id); ~Node(); void hi(); }; In a separate .cpp file that includes all the required headers, define them: #include “Tree.h” #include “Node.h” Node::Node(Tree * tree, int id) : tree_(tree), id_(id) { tree_->incCnt(); } Node::~Node() … Read more
First let’s start with how from import work in python: Well first let’s look at the byte code: >>> def foo(): … from foo import bar >>> dis.dis(foo) 2 0 LOAD_CONST 1 (-1) 3 LOAD_CONST 2 ((‘bar’,)) 6 IMPORT_NAME 0 (foo) 9 IMPORT_FROM 1 (bar) 12 STORE_FAST 0 (bar) 15 POP_TOP 16 LOAD_CONST 0 (None) … Read more
Maven does not allow cyclic dependencies between projects, because otherwise it is not clear which project to build first. So you need to get rid of this cycle. One solution is the one you already mentioned, to create another project. Another one would be to just move some classes from B to C or vice … Read more
While node.js does allow circular require dependencies, as you’ve found it can be pretty messy and you’re probably better off restructuring your code to not need it. Maybe create a third class that uses the other two to accomplish what you need.