Bad!APPL is a sample application that uses the QC API and illustrates some of the errors that QC can detect. These errors are common mistakes made in a lot of Macintosh applications today.
The version of BadAPPL shipped with QC is a fat binary and as such, will run native on both 68k and PowerPC Macs. Full source to BadAPPL is supplied along with the QCAPI for you to learn how the api works and how you might use it in your code. BadAPPL can be built with MPW, CodeWarrior, or Think/Symantec.
• Building BadAPPL
BadAPPL can be built using CodeWarrior (i.e. CW5) using the 'BadAPPL.68K.µ' or 'BadAPPL.PPC.µ' project files. Think C 6.0/7.0/8.0 builds can use the 'BadAPPL.π' project file. It can also be built with MPW (see below). In all environments, the 'BadAPPL.rsrc' file contains the needed resources for building BadAPPL. This rsrc file is automatically copied into the built stand alone app by all environments during a make.
BadAPPL can be built with MPW using the 'BadAPPL.make' file. There is a script called 'MakeBad' in the 'BadAPPL src' directory. Set the current directory to this directory and simply execute 'MakeBad' and it will do execute the make for you.
IMPORTANT: QC must be installed for BadAPPL to perform any kind of test control. Without QC installed, BadAPPL will politely disable functions that require QC to be present for them to be performed.
¥- The Think project layout is identical to the CodeWarrior projects (see below). So if you need to create a BadAPPL think project from scratch, see the listing below.
†- The CodeWarrior project is a CW5 project file. BadAPPL can be built with previous versions of CodeWarrior with the following project settings.
