wiki:Guidelines/MaintenanceGuidelines

Version 26 (modified by Paul A. Bristow, 13 years ago) ( diff )

More about GCC and importnace of locall suppression

  1. Motivation
  2. Introduction
    1. User code breaking cases
    2. Versioning individual Boost libraries
    3. Deprecating features
    4. Cross version testing
  3. Developer Guidelines
    1. Announce new library features
    2. Make feature request for each feature
    3. Document
      1. Tag Boost library with specific library version
      2. Include the tracked tickets on the Release notes
      3. List the test cases associated to the trac system tickets
      4. List the dependency upon other Boost library
      5. Document behavior differences between release and debug variants
      6. Document behavior differences between toolsets
    4. Coding
      1. Be careful with the use of using namespace header files
      2. Don't overload functions that are used by the TR1
      3. Avoid include-all-features files at the /boost level
      4. Don't refine functions overloading without ensuring the same behavior
      5. Avoid the inclusion of symbols at the boost or boost::detail namespace
      6. Avoid different external behavior depending on the variant release or …
      7. Avoid to change interfaces
      8. Don't delete files prematurely
      9. Don't delete namespaces prematurely
      10. Don't delete classes/functions/variables prematurely
      11. Don't modify functions prototypes prematurely
      12. Remove the deprecated features on a given release
    5. Test
      1. Test headers
      2. Don't forget to test
        1. The implicitly generated member functions
        2. The removed default member functions when you declare a constructor
        3. The deleted (private) default member functions
        4. The explicit constructors
        5. The implicit constructors or conversions
        6. The const-ness of variables, function parameters and function return …
      3. Separate the functional test from the unit test (implementation test)
      4. Preserve the functional test from the preceding versions
  4. User guidelines
    1. Don't use using directives
    2. Avoid the use of include all features files at the /boost level
    3. Help tracking regression test on the Trac system tickets
  5. Boosters guidelines
    1. Inspect the code
    2. Check that every modification has been documented
    3. Check that every modification has been tested
    4. Managing Warnings from Compilers (and other tools)
      1. Avoid warnings, Eliminate warning, Suppress Warnings, or Document.
      2. Specific Warnings and Suggested Actions.

MAINTENANCE GUIDELINES

WARNING: The contents of this page are not the result of a consensus of the Boost community.

Please feel free to improve this page directly or post on the Boost mailing lists ​boost-AT-lists.boost.org and ​boost-users-AT-lists.boost.org.

Motivation

To be added

Introduction

Nobody wants to completely disallow changes. We need them.

Everybody wants to avoid breaking changes, but sometimes these are also necessary.

This page describes guidelines that could help the Boost community to get stable libraries and as a consequence to avoid user code breaking when the user upgrades to a more recent Boost release.

The difference between breaking changes and bugs concerns documentation. A documented modification breaking user code cannot be considered a bug while the same undocumented modification could be a bug.

User code breaking cases

Why can user code break when the user upgrades to a more recent Boost release? Here are some examples which demonstrate the most common problems, although they do not pretend to be exhaustive.

  • Syntactic breaking: detected at compile time

It is evident that the removal of files, namespaces, classes, function, variables or macros could break user code. What it is less evident is that the addition of namespaces, classes, functions, variables at the namespace level or macros can also break user code. Note that modifications can be considered as deletion+addition.

The following code example 

#include <boost/file.hpp>
using namespace boost;

class foo {
  // ...
};

void bar() {
  // ...
}

breaks when

  • we add the namespace foo in file.hpp 
    // boost/file.hpp
namespace boost {
  namespace foo {
    // ...
  }
}
  • we add the class foo in file.hpp 
    // boost/file.hpp
namespace boost {
  class foo {
    // ...
  };
}
  • we add the function bar in file.hpp 
    // boost/file.hpp
namespace boost {
  void bar() {
    // ...
  }
}

Adding macros Use code should not break if we preserve the macro naming rule BOOST_LIBNAME_NAME.

  • Semantic breaking: detected at runtime

Sometimes user code will compile with the upgraded Boost release, but the code will not behave as before. Changes that can lead to this situation must be documented particularly prominently because the compiler can not help the user to catch the broken code.

The following code example 

#include <boost/file.hpp>
using namespace boost;


void bar(int i) {
  // ...
}

breaks when

  • we add the function bar in one of the files included by the user program 
    // boost/file.hpp
namespace boost {
  void bar(char c) {
    // ...
  }
}

These guidelines are not only addressed to Boost library developers, but also to users and the release manager team (RM). Every member of the Boost community has his role to play. Note that the author also plays the role of a user of all the libraries on which his library depends and of his own library when writing the library tests.

The key issues to get stable libraries are:

  • Versioning individual Boost libraries.
  • Using a deprecation period to give users notice that a breaking change is coming.
  • Documenting and tracking the changes.
  • Avoiding completely silent breakage by a deep inspection of code changes and running the regression tests (functional tests) from the _previous_ major release against the current release as a way to automatically detect and flag interface/behavioral changes.

These guidelines are related mainly to how to document changes, how breaking changes can be detected either by test or by inspections, and of course guidelines related to the code itself.

Versioning individual Boost libraries

This page don't contains any advice related to individual Boost libraries packaging. There is already the CMake project working on that. But tagging individual Boost libraries with a specific version MAJOR.MINOR.PATCH has already the informational advantage.

Versions are denoted using a standard triplet of integers: MAJOR.MINOR.PATCH. The basic intent is that MAJOR versions are incompatible, large-scale upgrades of the API. MINOR versions retain source and binary compatibility with older minor versions, and changes in the PATCH level are perfectly compatible, forwards and backwards.

Deprecating features

C++ don't have deprecated attributes, so the developer needs to emulate a warning when some deprecated feature is used. The #warning directive can be used to this purpose. 

  #warning "name is deprecated, please use new_name instead"

The main problem is that this warning will appear independently of whether the user code uses or not the deprecated feature. In order to palliate to this the inclusion of the deprecated feature could be accessible conditionally and only when included the warning will be reported or not.

For compatibility purposes deprecated features should be included by default. So the library behaves as if the features were not been deprecated. If a user don't want to include a deprecated feature he/she can define one of the following macros:

  • BOOST_DONT_INCLUDE_DEPRECATED: don't include any deprecated feature.
  • BOOST_DONT_INCLUDE_DEPRECATED_ON_X_Y: don't include any deprecated feature to be removed on version X.Y.
  • BOOST_LIBX_DONT_INCLUDE_DEPRECATED: don't include any deprecated feature for library Boost.LIBX.
  • BOOST_LIBX_DONT_INCLUDE_DEPRECATED_ON_X_Y: don't include any deprecated feature for libarary Boost.LIBX to be removed on version X.Y.
  • BOOST_LIBX_DONT_INCLUDE_DEPRECATED_NAME: don't include the deprecated feature name.

Once one of this macros is defined the developer can define another macro to make easier the work.

  • BOOST_LIBX_NAME_DECLARED: states that the deprecated feature name has been declared

Deprecated warnings are not reported by default, so the library behaves as if the features were not been deprecated. If the user wants this deprecated warnings to appear he/she can define one of the macros:

  • BOOST_WARNS_DEPRECATED: warms on all deprecated features
  • BOOST_WARNS_DEPRECATED_ON_X_Y: warms on all deprecated features to be removed on version X.Y

See the examples below.

Cross version testing

Running the regression tests from the _previous_ major release against the current release is a way to automatically detect and flag interface/behavioral changes. Sure, there are many potential problems with such an approach:

  • Some library tests are likely to also exercise code at the implementation/detail level.
  • Already limited testing resources (on the other hand, interface changes are likely to be detected by running such tests for a single, reasonably compliant, compiler).
  • ...

Another approach consist in preserving the test of the older releases and run them on the current release. If the developer needs to change the tests while she/he evolves his library this is a symptom the interface has been changed and the same way the tests are broken, the user code can also be broken. If the developer forbids himself to modify the test, he will be able to identify breaking changes early on.

Developer Guidelines

Announce new library features

It is a good idea the developer announce to the Boost mailing lists the new features just before committing in the release branch. This will let the time to the Boost community to inspect the modifications introduced.

Make feature request for each feature

Each modification deprecated/suppressed/modified/new feature should be tracked with a ticket on the Trac system.

Document

Tag Boost library with specific library version

Tagging each library release with a version, is the more visible way to signal possible incompatibilities to the user.

For example the thread library could have:

  • 2.1.0 Changes since boost 1.35
  • 2.0.0 Changes since boost 1.34
  • 1.0.0 Initial release on 1.25

Include the tracked tickets on the Release notes

The release notes should include

  • the list of all the bug tickets that have been solved
  • the list of all deprecated/suppressed/modified/new features with their associated tickets.

URL: ​https://svn.boost.org/svn/boost/website/public_html/beta/feed/history

There will be a file in that directory named boost_n_nn_n.qbk, where n_nn_n is the release number. Edit the [section Updated Libraries] portion of that file to add a description of changes to your library. For example: 

* [phrase library..[@/libs/interprocess/index.html Interprocess]:]
 *  Updated documentation to show rvalue-references functions instead of emulation functions.
 *  More non-copyable classes are now movable.
 *  Move-constructor and assignments now leave moved object in default-constructed state instead of just swapping contents.
 *  Several bug fixes:
  *[@https://svn.boost.org/trac/boost/ticket/2391 #2391] interprocess_recursive_mutex doesn't work interprocess,
  *[@https://svn.boost.org/trac/boost/ticket/2431 #2431] A Few More Corrections for the Interprocess Documentation,
  *[@https://svn.boost.org/trac/boost/ticket/1390 #1390] managed shared memory failing completely under OSX,
  *[@https://svn.boost.org/trac/boost/ticket/2570 #2570] boost::interprocess::message_queue::timed_send and timed_receive bug,
  *[@https://svn.boost.org/trac/boost/ticket/2528 #2528] Missing include of iostream in interprocess tests.

or 

* [phrase library..[@/libs/functional/hash/index.html Hash]:]
  * `boost/functional/detail/container_fwd.hpp` has been moved to
    `boost/detail/container_fwd.hpp`.
    The current location is deprecated.
  * For more detail, see the
    [@/doc/html/hash/changes.html#hash.changes.boost_1_38_0
    library changelog].

List the test cases associated to the trac system tickets

Each feature request or bug should have associated at least a test case. A table showing this association will help to check that each feature,bug is has the expected test coverage.

TicketSynopsisTest Case
#XXXXfoo foo foo bar bar bar test_foo_bar

List the dependency upon other Boost library

Each library lists the other libraries it depends upon and the minimum version # - as it does with compilers now

LibraryVersion #Build & LinkComment
Thread2.1.0linkgeneric lock()

Document behavior differences between release and debug variants

Document the differences in behavior that depends on the user defines, in particular the release and debug variants.

Document behavior differences between toolsets

Document the differences in behavior that depends on the toolsets.

Coding

Be careful with the use of using namespace header files

To import symbols from another namespace the developer can use the using directive using namespace but limited to the function level.

Don't overload functions that are used by the TR1

Overloading imported Boost.TR1 functions is equivalent to overload the std functions.

Avoid include-all-features files at the /boost level

Avoid include-all-file at the /boost level including all the functionalities of the library. Provide instead specific files at boost/lib/file.hpp.

If you provide such files ensure that your tests works when you include them directly or include the specific ones.

Don't refine functions overloading without ensuring the same behavior

If you need document them and warm the user.

Avoid the inclusion of symbols at the boost or boost::detail namespace

These symbols can collide with symbols of other libraries.

Announce them on the Boost mailing list when you think this is the best choice.

Avoid different external behavior depending on the variant release or debug without documenting it

Providing different external behavior depending on the variant release or debug could be a surprise for the user.

If you need them document it and warm the user.

Avoid to change interfaces

When you change the interface, you can see the changes that are needed at the Boost level, but you can not evaluate the cost induced by this change for the users. So before to change an interface deprecate it and let the user enough time to migrate to the new one.

Don't delete files prematurely

Before deleting a file, "file.hpp", deprecate it and let the user modify his code during some versions (e.g. until 1_40). Replace it by 

// boost/old_header_file.hpp
// include whatever file is needed to preserve the old file contents
#if defined(BOOST_WARNS_DEPRECATED) || defined(BOOST_WARNS_DEPRECATED_ON_1_40)
#warning "boost/old_header_file.hpp is deprecated, please include boost/new_header_file.hpp instead
#endif

It will be up to the user to define the macros BOOST_WARNS_DEPRECATED and BOOST_WARNS_DEPRECATED_ON_1_40 when the user wants to be warmed for deprecated features on Boost or on the Boost version 1.40 respectively.

Don't delete namespaces prematurely

Use the using sentence to import from the new namespace to the old one.

Don't delete classes/functions/variables prematurely

Instead of deleting a class or a public/protected function/variable on the next version protect its declaration by any of the DONT_INCLUDE_DEPRECATED macros. 

// boost/libx/header_file.hpp
namespace boost {
namespace libx {

#if defined(BOOST_DONT_INCLUDE_DEPRECATED) || defined(BOOST_DONT_INCLUDE_DEPRECATED_ON_1_41) \
 || defined(BOOST_LIBX_DONT_INCLUDE_DEPRECATED)  || defined(BOOST_LIBX_DONT_INCLUDE_DEPRECATED_ON_1_41) \
 || defined(BOOST_LIBX_DONT_INCLUDE_DEPRECATED_NAME)
#else
  #define BOOST_LIBX_NAME_DECLARED
  #if defined(BOOST_WARNS_DEPRECATED) || defined(BOOST_WARNS_DEPRECATED_ON_1_40)
    #warning "name is deprecated, please use new_name instead"
  #endif

  class name {
    name::name();
    // as before
  };
#endif

}
}

When the declaration should been included, the developer could define a BOOST_LIBX_NAME_DECLARED, which could be used on the class/function/variable definition. E.g. 

// boost/libx/header_file.cpp
namespace boost {
namespace libx {

#if defined(BOOST_LIBX_NAME_DECLARED)
  name::name() {
    // as before
  }
  // as before
#endif

}
}

Don't modify functions prototypes prematurely

Modifying an existing function prototype, if you were deleting it and adding the new one. Instead add the new when possible.

As both prototypes should coexist for some releases, check if this overloading could cause user code breaks.

Remove the deprecated features on a given release

Once the deprecated period is expired the developer sould remove them.

Don't forget to change the major version number.

Test

Test headers

Steve Watanabe has written a Jamfile that make easier this task. See /boost/libs/units/test/test_header for an example.

Include each header files twice The inclusion of a header file twice ensure that the file is self contained, and that it is well protected 

    #include <file.hpp>
    #include <file.hpp>
    int main() {return 0;}

Include all header files in both orders One more test could be useful, include all the Boost Headers files on both orders 

    #include <file1.hpp>
    #include <file2.hpp>
    ...
    #include <filen.hpp>

    #include <filen.hpp>
    ...
    #include <file2.hpp>
    #include <file1.hpp>

Link all the header files twice This ought to catch non-inlined functions and other duplicate definitions

Don't forget to test

The implicitly generated member functions

The implicitly generated member functions are part of your interface.

Add some simple tests that prove its correct behavior.

The removed default member functions when you declare a constructor

When you declare a constructor the other default constructors are not generated, so

The deleted (private) default member functions

The default member functions =deleted (or declared private) are not part of the interface.

Add some simple tests that prove the compilation fails when you use them.

The explicit constructors

The implicit constructors or conversions

The const-ness of variables, function parameters and function return types and functions

When a variable, function parameter or function return type is non-const, test that you can modify them.

When a variable, function parameter or function return type is const, test that you try to modify them the compilation fails.

Separate the functional test from the unit test (implementation test)

Functional test should take in account only the documented behavior. They can be used as regression test for new re-factorings of the implementation.

Implementation test can be used to test details in the implementation but not as regression tests.

Preserve the functional test from the preceding versions

While doing modifications to the library the developer can find some regressions on some tests of the preceding versions. It seems natural to change them to make the test succeed. This is not a good idea. The failing test is a symptom that the new modifications could break user code.

If the modification don't pretended to be an interface break, the developer should modify the library until the preceding test cases pass.

If the break is intentional move the tests to the failing tests compile_fail or run_fail on the Jamfile. The developer can copy the test and adapt it to the new interface. It could be a good idea to state explicitly on the test file name on which version they were included.

In order to avoid erroneous modification of the the released tests files the developer could change the rights of the test files. If the developer has no permission to do that on the SVN repository as a last resort he could change the permission in its own SVN copy.

User guidelines

Don't use using directives

As seen before, using directives in user code is one of the sources of user code breaking, so it will be safer to use namespace synonyms instead and prefix each symbol with them.

Instead of doing 

   using namespace boost::interprocess;

   shared_memory_object::remove("MySharedMemory");

do 

    namespace bip = boost::interprocess;

    bip::shared_memory_object::remove("MySharedMemory");

Avoid the use of include all features files at the /boost level

Avoid the use of include all features files at the /boost level use instead specific files at boost/lib/file.hpp. Including less code reduce your user code breaking chances.

Help tracking regression test on the Trac system tickets

A bug ticket should be associated to one or several test cases, either the test cases exists already and we are in face of a regression for some toolset, or a new toolset is considered, or a new test case is needed to reproduce the bug and the modification solve the problem. State clearly which test cases reproduce the bug it they exists and propose a new test case reproducing the bug otherwise.

Boosters guidelines

Inspect the code

Inspect the code to check that the new modifications don't include user code breaks. Tools comparing the contents of the current release and the preceding one could help. Discuss the issue on the ML and do a ticket on the Trac system if there is something to improve.

Check that every modification has been documented

Inspect that every modification has been reported on the documentation. Tools comparing the contents of the current release and the preceding one could help. Discuss the issue on the ML and do a ticket on the Trac system if there is something to improve.

Check that every modification has been tested

Inspect that every modification has been tested. Tools comparing the contents of the current release and the preceding one could help. Discuss the issue on the ML and do a ticket on the Trac system if there is something to improve.

Managing Warnings from Compilers (and other tools)

Avoid warnings, Eliminate warning, Suppress Warnings, or Document.

Boost aims to avoid warnings messages as far as is reasonably practicable, even when compiled with the highest and most pedantic warning level, avoiding vendor specific extensions if possible.

See also ​https://svn.boost.org/trac/boost/wiki/WarningFixes for progress on warning suppression.

Reasons to eliminate or suppress warnings:

1 To allow users, whose environment requires no warnings, to use Boost code.

2 To avoid the nuisance, perhaps overwhelming, of spurious warning messages.

3 To improve code quality by focusing library writers' attention on potential problems.

4 To improve portability by focusing developer attention on potentially non-portable code.

5 To improve compliance with the C++ Standard.

6 To permit users to set high warning levels when using Boost libraries without being overwhelmed with a barrage of library warnings.

7 To document that warnings have been considered by the library author or maintainer and are considered not significant.

8 For Boost, making the suppression local is more important than only suppressing a specific warning.

Of these, the last is possibly most important.

What to do

1 Test compilation with the most pedantic setting for the compiler.

For Microsoft Visual Studio, this means setting level to 4 (command line /W4).
For code that doesn't deliberately use Microsoft language extensions, disable them with Disable MS extensions = Yes, command line option /Za

To a jamfile add <toolset>msvc:<cxxflags>/Za # disable MS extensions.

If it proves impossible to compile with the /Za option (it is reported to cause trouble with the MS compiler, sometimes), just document this, including in the build jamfile.

If only one (or a few) modules in a test (or other) build require MS extensions, you can selectively 'switch off' this 'disable' in the 'requirements' in the jamfile, for example: 

# pow test requires type_of that MS extensions.
run pow_test.cpp ../../test/build//boost_test_exec_monitor
        : # command line
        : # input files
        : # requirements
          -<toolset>msvc:<cxxflags>/Za # Requires type_of which requires MS extensions, so cancel /Za.
        : test_pow
;

Note the leading - switches off the compiler switch /Za, producing output thus:

compile-c-c++ ..\..\..\bin.v2\libs\math\test\test_pow.test\msvc-9.0\debug\asynch-exceptions-on\threading-multi\pow_test.obj
pow_test.cpp
using native typeof

(You might also consider using Microsoft /Wall if available. You may find ​http://www.geoffchappell.com/viewer.htm?doc=studies/msvc/cl/c1xx/warnings/index.htm&tx=2,27&ts=0,3820 a helpful guide to the byzantine complexity of warnings).

For GCC this means -Wall -pendantic

but you might consider adding specific warnings that are to be suppressed, for example:

-pedantic -Wall -Wno-long-long -Wno-unused-value

but this is a global setting, so you need to document that these warnings must be suppressed by users of this module. This may be acceptable if they are building a library of entirely Boost modules.

Using bjam add warnings=all to the invocation command line.

Putting options in jam files allows setting to be made for one or more specified compiler(s).

Some sample options in jamfile.v2 are: 

project  
    : requirements 
      <toolset>gcc:<cxxflags>-Wno-missing-braces
      <toolset>darwin:<cxxflags>-Wno-missing-braces
      <toolset>acc:<cxxflags>+W2068,2461,2236,4070,4069 # Comments on warning message help readers who do not have ACC documentation to hand.
      <toolset>intel:<cxxflags>-nologo 
      <toolset>msvc:<warnings>all # == /W4
      <toolset>msvc:<asynch-exceptions>on # Needed for Boost.Test
      <toolset>msvc:<cxxflags>/Za # Disable MS extensions.
      #-<toolset>msvc:<cxxflags>/Za # (Re-)Enable MS extensions if these are definitely required for specifi module.
      #  The define of macros below prevent warnings about the checked versions of SCL and CRT libraries.
      #  Most Boost code does not need these versions (as they are markedly slower).
      <toolset>msvc:<define>_SCL_SECURE_NO_WARNINGS
      <toolset>msvc:<define>_SCL_SECURE_NO_DEPRECATE
      <toolset>msvc:<define>_CRT_SECURE_NO_WARNINGS
      <toolset>msvc:<define>_CRT_SECURE_NO_DEPRECATE
      #  Alternatively, you can just suppress the warnings (probably not the best way).
      <toolset>msvc:<cxxflags>/wd4996 # 'putenv': The POSIX name for this item is deprecated.
      <toolset>msvc:<cxxflags>/wd4512 # assignment operator could not be generated.
      <toolset>msvc:<cxxflags>/wd4224 # nonstandard extension used : formal parameter 'arg' was previously defined as a type.
      <toolset>msvc:<cxxflags>/wd4127 # expression is constant.
      <toolset>msvc:<cxxflags>/wd4701 # unreachable code - needed for lexical cast - temporary for Boost 1.40 & earlier.
   ...
    ;

Using warning-as-errors will make it hard to miss warnings.

Microsoft command line option /WX, gcc option -warning-as-errors gcc option -pedantic-errors

2 Consider each warning and

a Rewrite the code to avoid the warning, if possible. For example, adding a static_cast will indicate that any warning about loss of accuracy has been judged not possible or significant. Remove or comment out parameters to avoid warnings about unused parameters. Placing /* comment */ around an unused variable name, allows the name still to be useful documentation.

b Use the compiler specific mechanism to suppress the warning message, but try hard to ensure that this is as local to the package as possible so that users can still get warnings from *their code*.

For MSVC, this involves pushing to save the current warning state, disabling the warning, and later popping to restore (abbreviated as push'n'pop). 

#if defined(_MSC_VER)
#pragma warning(push) // Save warning settings.
#pragma warning(disable : 4996) // Disable deprecated localtime/gmtime warning.
#endif 

...

#if defined(_MSC_VER)
#pragma warning(pop) // Restore warnings to previous state.
#endif

Adding some or all of the warning message as a comment is helpful to tell readers what warning is being ignored, for example: 

#  pragma warning(disable: 4510) // default constructor could not be generated

If the warning is only for a specific compiler version, use this approach: 

#if BOOST_WORKAROUND(BOOST_MSVC, >= 1400)
#pragma warning(push)
#pragma warning(disable:4512) //assignment operator could not be generated
#endif

...

#if BOOST_WORKAROUND(BOOST_MSVC, >= 1400)
#pragma warning(pop)
#endif

c Repeat this process with other compilers and use their specific suppression methods.

d If a warning cannot be eliminated or suppressed, explain why in the code and the documentation. If appropriate, document in build files, as well. Consider indicating the highest warning level possible or compiler-specific settings that will provide a warning-free build.

Specific Warnings and Suggested Actions.

These are just few for starters, and need more, especially for gcc. Suggestions may be wrong!

The pragma or other code required to suppress warnings is in the right hand box, ready for copy and paste.

Microsoft

If you chose to suppress (rather than fix by recoding), localise the warnings as far as possible by using push'n'pop pragmas (see above).

WarningWarning DescriptionSuggestionsSuppression
C4100 unreferenced formal parameterEither surround the parameter with C comments, for example: int */ my_variable */)or just delete if the variable name is uninformative. If in other's module(s), or you are too busy/idle, at least suppress warning. In generic code you might not be able to comment the variable name as it might actually be used to call a static function. In this case simply referencing the variable (varname;) in the function body eliminates the warning.# pragma warning(disable: 4100) 'name' : unreferenced formal parameter
C4127 conditional expression is constantVery common and many believe unhelpful, but a few find it informative, so do not suppress globally. Even while(true) can trigger this! Suppress. while(true) can be rewritten as for(;;) eliminating the warning. # pragma warning(disable: 4127) conditional expression is constant.
C4180 qualifier applied to function type has no meaning; ignoredThis can always be suppressed - but check that you didn't mean to put the const somewhere else.# pragma warning(disable: 4180) qualifier applied to function type has no meaning; ignored
C4506 no definition for inline functionIf you cannot fix, suppress# pragma warning(disable: 4506) no definition for inline function
C4512 assignment operator could not be generatedSuppress using push'n'pop for the module(s) causing the warning. Adding the declaration (not the definition) of the appropriate operator=() as a private member does the trick as well.# pragma warning(disable: 4512) assignment operator could not be generated.
c4511 copy constructor could not be generatedThis can almost certainly be suppressed. # pragma warning(disable: 4511) copy constructor could not be generated
C4701 local variable may be used without having been initializedBest is to recode to avoid the message, but if you are very sure the message is misleading, suppress.# pragma warning(disable: 4701) local variable may be used without having been initialized
C4702 unreachable codeBe very cautious about suppressing this, but use of macros may make this troublesome, so suppress with care, and always locally.#pragma warning(disable: 4702) unreachable code
C4189 local variable is initialized but not referencedThis probably indicates a redundant variable and assignment, so probably remove it. If you are sure it is required (or has negligible cost for some documentation benefit), suppress.
C4224 nonstandard extension used : formal parameter 'arg' was previously defined as a type.This will bite users who try to compile with Microsoft extensions disabled. So is most undesirable, but may be a major nuisance to change the names in code.However fixing is the Right Thing, but meanwhile suppressing may be helpful.# pragma warning(disable: 4224) formal parameter 'arg' was previously defined as a type.
C4244 Conversion: possible loss of data.Fix, for example changing type or using static_cast is best, suppress with much caution.# pragma warning(disable:4244) Conversion: possible loss of data.
C4324 structure was padded due to declspec(align())Suppress#pragma warning(disable:4324) structure was padded due to declspec(align())
C4510 default constructor could not be generatedSuppress.# pragma warning(disable: 4510) default constructor could not be generated
C4535 calling _set_se_translator() requires /EHa Common from Boost.Test. Suppress warning in jamfile, add to project : requirements <toolset>msvc:<asynch-exceptions>on # calling _set_se_translator() requires /EHa
C4800 int' : forcing value to bool 'true' or 'false'Suppress. writing (intexpr ? true : false) helps as well# pragma warning(disable: 4800) int' : forcing value to bool 'true' or 'false'
C4996'putenv': The POSIX name for this item is deprecated.Many other messages about using secure versions.Unless you believe that the 'secure' versions are useful, suppress.# pragma warning(disable: 4996) was declared deprecated.

GCC

With GCC, it is more difficult to deal with warnings because there is no way (yet) locally silence individual warnings. It is considered important not to leave warnings switched off when meeting user code. This is an unresolved difficulty.

On the other hand, the number of unhelpful warnings seems fewer.

So more emphasis should be placed on fixing warnings, for example using static_cast, or providing missing items.

For a particular file,

#pragma GCC system_ No warnings from all this file, considered a system header.

or option --isystem

The -isystem command line option adds its argument to the list of directories to search for headers, just like -I. Any headers found in that directory will be considered system headers.

-Wsystem-headers

is effective until the end of the file.

Print warning messages for constructs found in system header files. Warnings from system headers are normally suppressed, on the assumption that they usually do not indicate real problems and would only make the compiler output harder to read. Using this command line option tells GCC to emit warnings from system headers as if they occurred in user code. However, note that using -Wall in conjunction with this option will not warn about unknown pragmas in system headers—for that, -Wunknown-pragmas must also be used.

The GCC docs say: "Also, while it is syntactically valid to put these pragmas anywhere in your sources, the only supported location for them is before any data or functions are defined. Doing otherwise may result in unpredictable results depending on how the optimizer manages your sources."

This might only mean you can't use them inside functions or class definitions, but it seems to imply that using them after a function definition leads to undefined behavior. Thus, even if we knew what setting to turn the warning back to (perhaps the warning wasn't enabled in the first place!), we might not be able to turn them back on.

<toolset>gcc:<cxxflags>-fdiagnostics-show-option # find out which options controls this warning (GCC >= 4.3)

#if defined(GNUC) GCC 4.3 and higher.

#pragma GCC diagnostic ignored "-Wdeprecated-declarations"

#endif

But that doesn't quite work, how do you know that the user wants -Wdeprecated-declarations to be set to "warning" after the include? Could be the user has disabled that one on the command line, in which case if we turn it back on, that's as annoying for the end user as warnings from Boost! There was a time when some MSVC std lib headers behaved like that, and believe me it was *seriously* annoying :-(

-Wall

This enables all the warnings about constructions that some users consider questionable, and that are easy to avoid (or modify to prevent the warning), even in conjunction with macros. This also enables some language-specific warnings described in C++ Dialect Options and Objective-C and Objective-C++ Dialect Options.

-Wall turns on the following warning flags:

-Waddress -Warray-bounds (only with -O2) -Wc++0x-compat -Wchar-subscripts -Wimplicit-int -Wimplicit-function-declaration -Wcomment -Wformat -Wmain (only for C/ObjC and unless -ffreestanding) -Wmissing-braces -Wnonnull -Wparentheses -Wpointer-sign -Wreorder -Wreturn-type -Wsequence-point -Wsign-compare (only in C++) -Wstrict-aliasing -Wstrict-overflow=1 -Wswitch -Wtrigraphs -Wuninitialized -Wunknown-pragmas -Wunused-function -Wunused-label -Wunused-value -Wunused-variable -Wvolatile-register-var

Note that some warning flags are not implied by -Wall. Some of them warn about constructions that users generally do not consider questionable, but which occasionally you might wish to check for; others warn about constructions that are necessary or hard to avoid in some cases, and there is no simple way to modify the code to suppress the warning. Some of them are enabled by -Wextra but many of them must be enabled individually.

-Wextra

This enables some extra warning flags that are not enabled by -Wall. (This option used to be called -W. The older name is still supported, but the newer name is more descriptive.)

-Wclobbered -Wempty-body -Wignored-qualifiers -Wmissing-field-initializers -Wmissing-parameter-type (C only) -Wold-style-declaration (C only) -Woverride-init -Wsign-compare -Wtype-limits -Wuninitialized -Wunused-parameter (only with -Wunused or -Wall)

The option -Wextra also prints warning messages for the following cases:

  • A pointer is compared against integer zero with <', <=', >', or >='.
  • (C++ only) An enumerator and a non-enumerator both appear in a conditional expression.
  • (C++ only) Ambiguous virtual bases.
  • (C++ only) Subscripting an array which has been declared `register'.
  • (C++ only) Taking the address of a variable which has been declared `register'.
  • (C++ only) A base class is not initialized in a derived class' copy constructor.

More information needed here!

? class does not have a virtual destructorSuppress or provide a virtual destructor.??

Intel

Information needed here.

Darwin /MacOS

Information needed here.

ACC

Information needed here.

Note: See TracWiki for help on using the wiki.