Sometimes as I add a new #include <*.h> file from the provided headers (eg pins.h), I get
'BOOL' does not name a type
I had this happening with the earlier rev of NBE, and had to go into the offending *.h and add
#include <ctypes> (?). Then the same error would pop up for the next *.h in the list, etc.
There must be a better way to handle this; do I somehow have old *.h's (I just upgraded to Rel23RC7) or do I need to put something in the properties or reorder my includes?
Thanks!
Sam
order of included headers, "'BOOL' does not name a type"
Re: order of included headers, "'BOOL' does not name a type"
You should not have to go into the "offending *.h" files and modify them. Just put the include file before the "offending file" and everything should be good.
Some files what things to be in a certian order.
You could create a master *.h file and put all of your includes into it in the order you want them and that they work. Then all you have to do is just include the master file.
Some files what things to be in a certian order.
You could create a master *.h file and put all of your includes into it in the order you want them and that they work. Then all you have to do is just include the master file.
Re: order of included headers, "'BOOL' does not name a type"
Thanks, that helped. Part of my problem was that I had an old project in my workspace that was giving me compile errors, but I wasn't looking there for problems since the errors weren't reported from there.
I would have thought that pins.h would have had to include basictypes.h to be compilable?
Sam
I would have thought that pins.h would have had to include basictypes.h to be compilable?
Sam