File: C:\dds\src\Research\cscout\example\awk\main.cDetails
Listings
FunctionsFile Dependencies
Include Files
Metrics
|
You can view a file's source code in five different forms:
int
|
int |
#if !defined(_ANSI_SOURCE) && !defined(_POSIX_SOURCE)
|
File MetricsWritable FilesNumber of elements: 13
Read-only FilesNumber of elements: 15
|
Read-only Files
You can bookmark this page to save the respective query CScout 2.0 - 2004/07/31 12:37:12 |
Writable Files
You can bookmark this page to save the respective query CScout 1.6 - 2003/06/04 15:14:51 |
static
) identifiers, but
detecting global identifiers is more tricky, since it requires
processing of all files that will be linked together.
The restriction to writable identifiers will filter-out noise
generated through the use of the system's library functions.
In our example, the following list is generated:
Files Containing Unused Project-scoped Writable IdentifiersMatching Files
You can bookmark this page to save the respective query CScout 2.0 - 2004/07/31 12:37:12 |
tab
to go to each hyperlink.
In our example the identifier will appear as follows:
|
setthetime
is declared as
static
, but not defined as such.)
static
) unused writable identifiers.
Although some modern compilers can detect file-local
identifiers, they fail to detect macros and some types of
variable declarations.
The CScout query is more general and can be more reliable.
The restriction to writable identifiers will filter-out noise
generated through the use of the system's library functions.
In our example, the following list is generated:
Files Containing Unused File-scoped Writable IdentifiersMatching Files
You can bookmark this page to save the respective query CScout 2.0 - 2004/07/31 12:37:12 |
copyright
and the rcsid
identifiers.
|
#ifdef
'd out.
In our example, the result set only contains the processing script (the compiled workspace definition file).
Writable .c Files Without Any StatmentsYou can bookmark this page to save the respective query CScout 1.6 - 2003/06/04 15:14:51 |
#pragma
commands)
to drive the CScout's source code analysis.
In our case the results are:
Writable Files Containing Unprocessed Lines
You can bookmark this page to save the respective query CScout 2.0 - 2004/07/31 12:37:12 |
In our case the results are:
Writable Files Containing Strings
You can bookmark this page to save the respective query CScout 1.6 - 2003/06/04 15:14:51 |
#include
invocations.
This query can be used to find files that break such a guideline.
As usual, read-only system files are excluded; these typically
use recursive #include
invocations as a matter of course.
In our example, the result is:
Writable .h Files With #include directivesYou can bookmark this page to save the respective query CScout 1.6 - 2003/06/04 15:14:51 |