Wim Veldhuis wrote in a message to Mike Bilow:

 PH> Drat!  I think you're right.  Oh well, I was just
 PH> unlucky/stupid enough to have chosen  and  for
 PH> two of my own files, so I'll just nip in and change 150-odd
 PH> source files :-(.  

 MB> There's always the rather vicious "#define 
 MB> " approach...  

 WV> Yep, but macro expansion does not work inside string
 WV> literals. At least not in Borland C++, but I wouldn't be
 WV> amazed if it didn't work in other compilers also. 

Macro expansion of preprocessing tokens on an #include line is required by
ANSI, except in cases where the corner brackets or quote marks appear.

The official ANSI rule (6.8.2) is:

   The method by which a sequence of preprocessing tokens between a 
   preprocessing token pair or a pair of " characters is combined into a
   single header name preprocessing token is implementation-defined.

The following is given by ANSI as an example which must be supported:

#if   VERSION == 1
      #define INCFILE "vers1.h"
#elif VERSION == 2
      #define INCFILE "vers2.h"
#else
      #define INCFILE "versN.h"
#endif
#include INCFILE

If Borland does not handle this correctly, it is a reportable bug.
 
-- Mike


---