Lines Matching full:effect
798 effect.
1068 effect in the primary source file.
1163 definitions take effect at the place you write them. Therefore, the
1197 effect:
1458 If the argument is empty, that `##' has no effect.
1596 the differences from C99. To get the same effect with both this and
1868 make sure that programs will execute with the same effect whether
2132 the macro name. `#undef' has no effect if the name is not a macro.
2197 definition takes effect in time for argument pre-expansion, but the
2385 When you use this macro with an argument containing a side effect,
2457 effect of causing the program to add 4 to the value of `foo' wherever
2508 Most of the time, this has no effect. If the argument contained any
3028 effect. In addition, FILENAME is a string constant. The
3045 Predefined Macros::. They do not have any effect on `#include''s idea
3112 has the same effect as `#pragma GCC dependency "parse.y"'. The same
3113 effect could be achieved using macros, for example
3189 understood as a preprocessing directive but has no effect on the
3381 careful to do it in such a way that the observed effect is identical
3385 have no special meaning. As explained later, an effect similar to
3438 preserved. Here is an example of using a comment to effect token
3766 effect.
3895 `-I foo' have the same effect.
3961 (Both forms have the same effect.)
4145 dependency output file as a side-effect of the compilation process.
4376 command line, this option has no effect, since no `#line'
4451 directive line have the effect of turning that line into an
4540 `CPATH' is `:/special/include', that has the same effect as
4692 has no effect on the meaning of this License.
