If anyone is interested, one of the consequences of the fact that
  Borland C++ 2.0 for OS/2 includes the OS/2 Developers' Toolkit 2.0
  (where every other C++ compiler for OS/2 uses release 2.1 or 3.0) is
  that perfectly correct C++ programs may fail to compile.

  One of the bugs in Toolkit 2.0, that was fixed in Toolkit 2.1, is the
  definition of the NULL macro in OS2DEF.H.  When you are using C++, and
  you have included  before any other headers (as is common
  practice for some people), the macro is not defined correctly.

  You can apply by hand the fix from XR0210 (i.e. Toolkit 2.1), by
  editing line 75 of \BCOS2\INCLUDE\OS2DEF.H to read

      #ifdef __cplusplus   /* XR0210 patch applied */

  instead of

      #ifdef _cplusplus

  and C++ programs that use NULL should now compile.

  Those who used IBM CSet++ 2.0 with Toolkit 2.0 will be familiar with
  this problem, but will wonder why it still persists in Borland C++ 2.0
  for OS/2, when it disappeared as a problem for everyone else almost
  two years ago.

  You can tell that I've just had a frustrating waste of time porting
  something to Borland C++ for OS/2, can't you ?

  Incidentally, when informed of this bug, Borland thanked me for
  reporting it, but wouldn't tell me whether they would release any
  fixes for the product.

   > JdeBP <
___
 X MegaMail 2.10 #0:
--- Maximus/2 3.00