Professional #include contents

Question

I need to create an API that will allow my customer\'s developers to use a proprietary C module that will be released as a library (think .lib or .so -

Answer 1

Please pretty please make sure you don't (re)define symbols that might be defined anywhere else. I don't mean just the standard names, please prefix all symbols declared/defined in public headers with a specific string and avoid any name that anybody else might have ever though about using.

I say this after seeing too much craziness like this in "professional" publicly available headers:

typedef unsigned short uchar;