Compiler terminates with "Assertion failure" message when compiling certain constructs. Linker terminates with "Assertion failed" message on object files larger than approx. 4Mb. Borland Quality Central report numbers 393 and 793.

Apply Service Pack 3 or later. Disable language extensions (/Za). Enable exceptions and RTTI (/GX /GR). Add compiler option /Zm500.

Compiler may fail to compile code for large expressions and large if-statements; a compiler error message is generated in these cases.

Much of the ANSI C++ library (e.g. <locale>) fails to compile with Microsoft language extensions disabled. This may cause problems in the future.

No known optimisation problems with code generated by Perfect Developer.

See here for detailed configuration information.

The compiler generates spurious C2039 messages (" 'X': is not a member of 'Y' ") when encountering expressions of the form "e -> X :: f()" where 'X' is an ancestor class of the type of 'e' and 'f()' is a public member of 'X'. We have not found a workaround for this problem.

The compiler may also produce C1001 "INTERNAL COMPILER ERROR (compiler file 'f:\vs70builds\3077\vc\Compiler\Utc\source\P2\main.c', line 148)" messages, which can be cleared by disabling optimisation.

Use Perfect Developer version 3.0 or later. Disable language extensions (/Za). Enable RTTI (/GR). Warning level 4 may be used (/W4). No known problems using optimisation level 2 (/O2). You will need to recompile the Perfect Developer library, since the precompiled library supplied on the CD is built using Visual C++ 6.0 and is not compatible with VC++ 2005. If compiling for 64-bit (AMD64) platforms, use Perfect Developer 3.02 or later and recompile the library in 64-bit mode.

Incorrectly instantiates unused members of class templates. Compiler is now in the process of being released as an open source project.

Incorrectly generates excess destructor calls.

This is a not an official release; it is a snapshot of the development path leading to GCC 3.0.

Enabling any optimisations is liable to cause incorrect code to be generated.

Compiler incorrectly generates excess destructor calls within conditional expressions. Use Perfect Developer 1.10 or later and set compiler type to "gcc" to avoid generation of code that gcc is known to compile incorrectly.

Do not use gcc optimisation level 3.

It is not yet clear whether the problem with excess destructor calls generated by earlier versions of gcc within conditional expressions is completely fixed. For now we recommend configuring Perfect Developer code generation for compiler type "gcc" to avoid possible problems in this area.

Optimisation level 3 appears to be safe.