In article <11*********************@m7g2000cwm.googlegroups.c om>,
CoL <ap***********@gmail.comwrote:
>Thats correct Richard and Ian....its exactly that only. Thats what
defining a macro in the header file should work but thats exactly we
dont want to modify the
third party header.. :(
Their code's wrong, so it *ought* to be modified.
If the header doesn't (directly or indirectly) include <errno.h>
itself, and you can modify the file that includes the header, you
could put
#define errno some_junk
before the #include and
#undef errno
after it. That way the header would just declare some_junk instead.
Alternatively perhaps you could avoid including their header
altogether and declare the necessary things from it yourself?
Obviously this will cause problems if they modify it later.
-- Richard
--
"Consideration shall be given to the need for as many as 32 characters
in some alphabets" - X3.4, 1963.