Changes between Version 14 and Version 15 of Guidelines/WarningsGuidelines
- Timestamp:
- Jan 15, 2011, 4:15:52 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Guidelines/WarningsGuidelines
v14 v15 699 699 Both of them should be used only at file scope for versions 4.2-4.5. Beginning at version 4.6 they can be used at any scope. If you want to turn multiple things from warning to error to ignored between the push and the pop then this will not be effective for you. 700 700 701 It allows you to do things like :701 It allows you to do things like (for GCC version 4.6 or later): 702 702 {{{ 703 703 GCC_DIAG_OFF(sign-compare); … … 727 727 }}} 728 728 729 These are perhaps not the best choice of names for the macros since they risk future collision with GCC macros. In your domain you should probably prefix every instance of GCC_ with YOURDOMAIN_ to make YOURDOMAIN_GCC_, for example YOURDOMAIN_GCC_DIAG_OFF(x).729 These macro names won't collide with GCC macros since their's start with one or two underscores. 730 730 ---- 731 731 '''Intel'''