FiveWin++ for Xbase++

FW++ includes on the same box the 16 & 32 bits libraries for CA-Clipper and Alaska XBase++.

With this new product you can generate 32bits executables, using the same FW syntax and having full backward source code compatibility.

FW++ is not compatible with CA-Clipper. FW++ is a specific library for Alaska XBase++.

FW++ 2.4 is only compatible with the latest version of Alaska XBase++ 1.8 and above.

Conversion steps to use FW++

• It uses the same header files as FW, and the same goes for the source code (both PRG and C modules). FW and FW++ use exactly the same source code modules.

• Recompile all your FW PRGs. Simply replace clipper.exe for xpp.exe. All your PRGs should compile without errors and warnings on first try, except on those places where you have the token '3D'. XBase++ does not accept command tokens that start with a number. Rename '3D' into '_3D'.
  
  Check that the environement variables INCLUDE and LIB point to XBase++ directories and not the ones from CA-Clipper.

• If you have developed your own PRG classes then you need to do some modifications as there are some differences between FW Objects engine and XBase++ own OOP engine. Simply review any FW Class PRG to see the easy modifications needed to make them fully compatible.
  
  For example, due XBase++ supports multiple inheritance the use of 'Super' is not directly valid, for that you should include the following instruction:
  
  #ifdef __XPP__
  #define Super ::TSuperClass
  #endif
  
  Where ::TSuperClass should be replaced with the parent class name.

• To link your app you just need to use Five32rt.lib (instead of Five.lib, FiveC.lib, Objects.lib and WinApi.lib). To run the EXE, Five32rt.dll should be on the app location, or at windows directory. If your app is too big for Alaska Alink.exe, then you should split your app and build DLLs. We provide several samples and make files to do this.
  
  Alaska has provided a 'xppfilt.exe' to easy this process (works very well!). You may not be able to link cause some unresolved externals. If this is your case please lets us know, so we may review Five32rt.lib and we will send you a new one inmediately (14Kb as a zip file).

• Resources RC files are 100% compatible. Simply use Borland BRC32.EXE instead of rc.exe or brc.exe.
  Borland BRC32.EXE is included in all Borland products (C/C++, Delphi, ...)

• If you use resources inside DLLs, then you must upgrade your resources DLL to a 32 bits one. FW++ provides an empty 32 bits DLL to be used for this purpouse. Open your actual DLL 16 bits resources file using Borland Resource Workshop and then save it as a .RC file. Then use Borland Brc32.exe to place your .RC file into DLL 32 bits.

That is all! Once your EXE is ready, then fasten your seatbelt, relax, doble click on the icon and be ready for the most impressive 16 bits to 32 bits conversion experience ever seen.