??? 06/08/10 21:44 Modified: 06/08/10 21:45 Read: times |
#176529 - I would not Responding to: ???'s previous message |
It appears that the solution is to place all module-wide configurations in a separate header file, and then to #include this file in the parent module, as well as in each of the, possibly numerous, sub-component header files.
// file blah.c #include "jobdefines.h" #include "blahdef1nes.h" is, at least in my opinion, a lot cleanter than including jobdefines in blahdef1nes simply because most files will not have a 'local' defines.h. If you start insisting on local define files you will end up with a lot of files of one line such as file1defines will have one line #include jobdefines and nothing else Erik PS include the SFRs in jobdefines, they are global whatever else you do. that will get rid of the "conditional SFR definition. BTW I AM curious, why do you not use a global SFR definition .h file? |