Borland

next - skip - up - start

Borland C++ 3.1, 4.5, 5.02: Recently this has been my main development platform, so naturally everything works with this compiler. There was a problem with the library utility in version 2.0 which is now fixed. You will need to use the large or 32 bit flat model. If you are not debugging, turn off the options that collect debugging information. Make sure you don't run Borland's exceptions and my simulated exceptions at the same time.

If you are using version 5 remember to edit include.h to deactivate my Boolean class.

When running my test program under ms-dos you may run out of memory. Either compile the test routine to run under easywin or use simulated exceptions rather than the built in exceptions. Under easywin the test program indicates a memory leak. I presume this is partly because of the way windows organises its heap rather than there being a real problem.

If you can, upgrade to windows 95 or window NT and use the 32 bit console model.

If you are using the 16 bit large model, don't forget to keep all matrices less than 64K bytes in length (90x90 for a rectangular matrix if you are using double as your element type). Otherwise your program will crash without warning or explanation. You may need to break the tmt set of test files into two parts to get the program to fit into your computer.

In version 4.5, under easywin the automatic clean-up of objects by the exception mechanism does not seem to work correctly. Use my simulated exceptions if this is a problem.

One version of Borland had DBL_MIN incorrectly defined. If you are using an older version of Borland and are getting strange numerical errors in the test programs reinstate the commented out statements in precision.h.

I include make files that work under Borland 4.5 and 5. You will need to edit these to correctly locate the directories for the include and library files. Both assume you are using simulated exceptions. BC.MAK also works with version 3.1 if you delete the options that are not recognised and the reference to the library file that is not recognised.

C++ Builder version 4: I have successfully used this using the console wizard (menu item file/new - select new tab). Either use namespace or rename a couple of my exception names that conflict with Borland. Use compiler exceptions. Suppose you are compiling my test program tmt. Rename my main() function in tmt.cpp to my_main(). Rename tmt.cpp to tmt_main.cpp. Borland will generate a new file tmt.cpp containing their main() function. Put the line int my_main(); above this function and put return my_main(); into the body of main().

next - skip - up - start