If you include one .h file, should that ever force you to include another .h file as well? Or would that never happen in good design?
For example. Suppose you have a compiler error:
So you look up where T_UINT32 is defined and you add the following to the top of your file:Code:myfile.h: error: 'T_UINT32' undeclared (first use in this function)
Then when you try to compile you get another error:Code:#include "mytypes.h"
All .h files have proper header guards in them. I am running into a situation like this and it does not make sense to me. Does this imply an error in a .h file somewhere?Code:In file included from myfile.h from mytypes.h:h:252: error: expected specifier-qualifier-list before 'uchar'