Lines Matching full:effect
797 effect.
1030 effect in the primary source file.
1125 definitions take effect at the place you write them. Therefore, the
1159 effect:
1420 If the argument is empty, that `##' has no effect.
1558 the differences from C99. To get the same effect with both this and
1826 make sure that programs will execute with the same effect whether
2050 the macro name. `#undef' has no effect if the name is not a macro.
2115 definition takes effect in time for argument pre-expansion, but the
2303 When you use this macro with an argument containing a side effect,
2375 effect of causing the program to add 4 to the value of `foo' wherever
2426 Most of the time, this has no effect. If the argument contained any
2946 effect. In addition, FILENAME is a string constant. The
2963 Predefined Macros::. They do not have any effect on `#include''s idea
3030 has the same effect as `#pragma GCC dependency "parse.y"'. The same
3031 effect could be achieved using macros, for example
3107 understood as a preprocessing directive but has no effect on the
3299 careful to do it in such a way that the observed effect is identical
3303 have no special meaning. As explained later, an effect similar to
3356 preserved. Here is an example of using a comment to effect token
3691 effect.
3858 `-I foo' have the same effect.
3922 (Both forms have the same effect.)
4107 dependency output file as a side-effect of the compilation process.
4327 command line, this option has no effect, since no `#line'
4391 directive line have the effect of turning that line into an
4480 `CPATH' is `:/special/include', that has the same effect as
4632 has no effect on the meaning of this License.
