I'm trying to compile some code that uses cstring with the Borland C++ compiler. Borland insists I write the include as # include <cstring.h>. What puzzles me especially is that the Borland include directory has a file named cstring, which, in a comment, states that the syntax cstring.h is for backwards compatibility only.
Anyway, what goes on in Borland's internal doesn't interest me. What does interst me is not having to rewrite lots of code that works other compilers. Is there any way, possibly by downloading my own header files, I can convince Borland to accept # include <cstring>?
Anyway, what goes on in Borland's internal doesn't interest me. What does interst me is not having to rewrite lots of code that works other compilers. Is there any way, possibly by downloading my own header files, I can convince Borland to accept # include <cstring>?
