Lines Matching refs:constraints

8 [section:vmd_constraints Macro constraints]
20 if it does not. This is all part of the constraints for any callable in C++ and should
33 does not follow the constraints for a macro parameter, as specified in the 
52 to determine if the input meets the constraints which the preprocessor metaprogrammer places on it …
56 This does not mean that one should give up attempting to check macro input constraints. If it can b…
58 …straint checking macros. But the most important thing when dealing with macro input constraints is 
59 …ey should be carefully documented, and that the programmer should know that if the constraints are 
63 flexibility, allows that erroneous results could occur if certain input constraints are not met, wh…
65 everything that the preprocessor is capable of doing to check the input constraints, and carefully …
68 Documented macro input constraints are just as valid in the preprocessor as 
69 compile-time/run-time constraints are valid in C++, even if the detection of such constraints 
70 and/or the handling of constraints that are not met are far more difficult,
73 The VMD library uses constraints for most of it macros and the documentation for those macros
74 mentions the constraints that apply in order to use the macro.