TASKING VX-toolset for ARM User Guide

TASKING VX-toolset for ARM User Guide#if TESTint i;#endifHere, the first token that does not belong to a preprocessing directive is again int, but the header stoppoint is the start of the #if block containing it. The PCH file will reflect the inclusion of xxx.h andconditionally the definition of YYY_H and inclusion of yyy.h; it will not contain the state produced by #ifTEST.A PCH file will be produced only if the header stop point and the code preceding it (mainly, the headerfiles themselves) meet certain requirements:• The header stop point must appear at file scope -- it may not be within an unclosed scope establishedby a header file. For example, a PCH file will not be created in this case:// xxx.hclass A {// xxx.C#include "xxx.h"int i; };• The header stop point may not be inside a declaration started within a header file, nor (in C++) may itbe part of a declaration list of a linkage specification. For example, in the following case the headerstop point is int, but since it is not the start of a new declaration, no PCH file will be created:// yyy.hstatic// yyy.C#include "yyy.h"int i;• Similarly, the header stop point may not be inside a #if block or a #define started within a headerfile.• The processing preceding the header stop must not have produced any errors. (Note: warnings andother diagnostics will not be reproduced when the PCH file is reused.)• No references to predefined macros __DATE__ or __TIME__ may have appeared.• No use of the #line preprocessing directive may have appeared.• #pragma no_pch (see below) must not have appeared.• The code preceding the header stop point must have introduced a sufficient number of declarations tojustify the overhead associated with precompiled headers.The minimum number of declarations requiredis 1.78