When I have doubts as to the inclusion of a header section due to=20
#ifdefs, I'll frequently add #emit or #warn directives to the file in a=20
suspect section

#ifdef NTH_LEVEL_DEFINE
// I wonder if this is included???
#warn nth_level_define IS included
....
#else
#warn nth_level_define NOT included

....
#endif

Joe Wronski

On 9/3/2014 2:03 AM, Ruben J=F6nsson wrote:
>> On 02/09/2014 15:31, Harold Hallikainen wrote:
>>> I'm messing with CustomSNMPApp.c and apparently messed it up somewhere
>>> (missing #endif). So far, I've printed it out and marked the #ifdef,
>>> #else, #endif blocks by hand as lines in the left margin. Since Microch=
ip
>>> nests these several deep, it's easy to mismatch them.
>>>
>>> Is there a source file lister that will do something similar (pair thes=
e
>>> up through nesting) so I can figure out where I went wrong? I see that
>>> MPLABX and Notepad++ let you collapse blocks, but it's still pretty har=
d
>>> to see where the problem is.
>>>
>>> THANKS!
>>>
>>> Harold
>>
>> Harold,
>>
>> Code::Blocks is a nice IDE that shows the #if or #else block that is not
>> included in compilation in a fainter shade (the header files with the
>> definitions you use in the #if must be accessible).
>>
>>
>> Best regards,
>>
>> Isaac
>>
> MPLABX also does this.
>
> /Ruben


--=20
Joe Wronski
jwronski@stillwatereng.net
www.stillwatereng.net

--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.