Quote Originally Posted by ridgerunnersjw View Post
I am using Code Composer Studio IDE.....not sure that <filename> vs "filename" isn't more the norm than the rule....That is I can put "string.h" OR <string.h> and code works either way....I suspect you have to set something up under compiler options to over-ride the norm which is to not really care how the user includes header files. Point being if you didn't do it right you could easily make "public.h" exposed as well or worse <private.h> gets exposed.
With <> only the include file path is scanned.
With "" the current directory is first scanned, then the include file path is scanned.

I would keep the private file in with your source, and the public file somewhere in the include path.

See Include Syntax (The C Preprocessor)