Hi, I thought about it again.
I think according to my design experience that it is wrong to do this:
ModuleA.ipp -- includes --> ModuleA.h
ModuleB.ipp -- includes --> ModuleB.h
main.cpp:
Code:
#include "MouduleA.ipp"
#include "MouduleB.ipp"
The reason is that any code from ModuleA cant use access code from ModuleB because the declarations for ModuleB are not yet defined.
And this is not for Object Oriented approach.
I even dont agree at all with Object Oriented approach. It is an issue for non OO approach.
The idea I suggest is:
ModuleA.h
ModuleB.h
ModuleA.ipp
ModuleB.ipp
main.cpp:
Code:
#include "MouduleA.h"
#include "MouduleB.h"
#include "MouduleA.ipp"
#include "MouduleB.ipp"
This is the way I used to write code in a Tool I sell, written in Autoit.
In Autoit I did exactly the same but with "Globals" naminng convention:
#include "MouduleA.Globals.au3"
#include "MouduleB.Globals.au3"
#include "MouduleA.au3"
#include "MouduleB.au3"
Is it known approach in C++ world?