Single-File Templates

In one text file, coverage information for directories, source files and functions is structured. Functions are the smallest reporting entity, there is no equivalence to source code view.

The file extension of the template determines the default file extension of the output file - there is no format semantic associated with it by ctcreport. You can create templates for all text based formats, like JSON, CSV, XML, YAML etc.

For file extensions .html and .xml, ctcreport translates all characters "&", "<" and ">" (from function names, source code, user variable values etc.) to "&amp;", "&lt;" or "&gt;", respecitvely.

Variables are used in $...$ like in structured templates. Loop controls are enclosed in {…} instead of HTML comments:

{CTC_LOOP("Symbolfiles")}
FileName: $FileName$
Instrumentation Time: $InstrumentationTime$
{CTC_LOOP_END("Symbolfiles")}