> That's why you often see interlocks on include files.


 Then the use of interlocks is not required if the caller includes the
necessary files.  Is my understanding correct.


>
> Personally I don't like this method.  Include files shouldn't include other
> include files.  The dependencies should be published and the caller should
> include the necessary files.


Does "published" refer to documenting dependencies in a comment block.

I have virtually zero experience here so I am not aware of the pros and cons
of both approaches.  However, I would prefer to see all the dependencies
listed in the include section.

As a novice, I found it difficult to follow what was using what in the case
of the Microchip TCPIP Stack.

/Ruben commented

"By using this include scheme I don't need to care about that here
since including of sub modules is all handled automatically"

but so far I seem to have a need to examine what is in the sub modules and
their purpose so I can taylor the project for my needs.

I thought this was because I am a novice but I can see no way to escape it.
I need to examine the _NODE_INFO structure (for example) somehow (which is
buried deep) so I can use it to stuff with values to use for my purposes.

Cheers Justin






>
>
> ********************************************************************
> Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products
> (978) 742-9014.  Gold level PIC consultants since 2000.
> --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist