staticwithin a file will not interfere with identifiers outside that scope. Thus, the following example will print 3 and not 7.
In addition, C also partitions a program's identifiers into four namespaces. Identifiers in one namespace, are also considered different from identifiers in another. The four namespaces are:
struct/union(actually a separate namespace is assigned to each
ididentifier instances are different:
Normally when you want to locate or change an identifier name, you only consider identifiers in the same scope and namespace. Sometimes however, a C preprocessor macro can semantically unite identifiers living in different namespaces, so that changes in one of them should be propagated to the others. The most common case involves macros that access structure members.
idinstances should be propagated to all others for the program to retain its original meaning. CScout understands such changes and will propagate any changes you specify accordingly.
Finally, the C preprocessor's token concatenation feature can result in identifiers that should be treated for substitution purposes in separate parts. Consider the following example:
xin one of the
coordmacro invocations should replace the
xpart in the
xrightvariables. Again CScout will recognize and correctly handle this code.
|Contents||« Previous Next (Identifier Elements) »|