AB>
  > A long time ago i purchased BC++/2 1.0, some parts are outdated
  > and i want to replace them with the stuff that comes with the
  > warp developper kit.
AB>

  Customising the OS/2 Developers' Toolkit to a specific C++ compiler
  involves three major steps.

  Firstly, you need to alter OS2DEF.H to define the calling convention
  macros in terms of whatever calling convention keywords are provided by
  your compiler.  The SYSTEM calling convention, for example, requires the
  __stdcall keyword in Borland C++, _System in IBM VisualAge C++,
  __syscall in Watcom C++, and no keyword in MetaWare High C++.

  Secondly, you need to ensure that you have accounted for whether your
  C++ compiler defaults `char' to `signed' or `unsigned' in the definition
  of "character" types such as BYTE.

  Thirdly, you need to ensure that the libraries and headers have the
  names that the rest of your compiler's toolset expects to see.  For
  example, the 32-bit OS/2 system API import library is called OS2386.LIB
  in the toolkit, but Borland's tools expect it to be called OS2.LIB and
  that is the library that they will go looking for.

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