A number of the Insure++ options can specify filenames for various configuration and/or output files. You may either enter a simple filename or give a template which takes the form of a string of characters with tokens such as %d, %p, or %V embedded in it. Each of these is expanded to indicate a certain property of your program as indicated in the following tables. The following table lists the options that can be used at both compile and runtime:
| Key | Description | Examples |
|---|---|---|
%a | Machine architecture you are running on. | Windows:
Unix:
|
| Abbreviated name of the compiler you are using. | Windows:
Unix:
|
%r | Insure++ version number. | 7.5 |
%R | Insure++ version number without periods (.) | 75 |
The following table lists tokens that are only available at runtime:
| Key | Description |
|---|---|
%d | Time of program compilation in format: YYYYMMDDHHMMSS |
| Time of program execution in format: YYYYMMDDHHMMSS |
%n | Integer sufficient to make filename unique, starting at 0 |
%p | Process ID |
%v | Name of executable |
%V | Directory containing executable |
Examples
The name template report_file %v-errs.%D when executed with a program called foo at 10:30 a.m. on the December 21, 2018, might generate a report file with the name fooerrs. 20181221103032. The last two digits are the seconds after 10:30 on which execution began. You can also include environment variables in these filenames.
For TCA, the option coverage_map_file tca.map.%a.%c may generate a report file with the name tca.map.Win32.cc on Windows or tca.map.sun4.cc on Unix.
You can also include environment variables in these filenames so that the following option generates the same filename as the previous example:
HOME/tca/tca.map.%a.%c
This option also ensures that the output is placed in the tca sub-directory of the user’s home directory.
