Master list of macro and symbol collision issue reports in all Boost libraries

[ned14]

Hopefully github will draw a line through each of these as/if they get closed so one can see an overview of progress. When/if they are all closed, build tooling ought to add a build-time check to prevent breakage of Boost library guidelines in the future.

• List of non BOOST-prefixed macros container#136
• List of non BOOST-prefixed macros date_time#118
• List of non BOOST-prefixed macros exception#28
• List of non BOOST-prefixed macros fusion#218
• Prefix macros with BOOST_ gil#410
• List of non BOOST-prefixed macros graph#193
• List of non BOOST-prefixed macros iterator#53
• List of non BOOST-prefixed macros lambda#18
• List of non BOOST-prefixed macros math#278
• List of non BOOST-prefixed macros multi_array#25
• List of non BOOST-prefixed macros parameter#94
• List of non BOOST-prefixed macros phoenix#90
• List of non BOOST-prefixed macros polygon#33
• List of non BOOST-prefixed macros program_options#88
• List of non BOOST-prefixed macros property_map#12
• List of non BOOST-prefixed macros python#281
• List of non BOOST-prefixed macros qvm#22
• List of non BOOST-prefixed macros serialization#185
• List of non BOOST-prefixed macros spirit#562
• List of non BOOST-prefixed macros stacktrace#85
• List of non BOOST-prefixed macros thread#302
• Injection of non-boost namespaces into global namespace type_traits#135
• List of non BOOST-prefixed macros wave#52

[apolukhin]

Can the boost.inspect tool be tought to detect non BOOST_ prefixed maceo?

[apolukhin]

Can the boost.inspect tool be tought to detect non BOOST_ prefixed maceo?

Oh, you've already done a PR #353

[hkaiser]

I would like to suggest to exclude macro symbols that are used as #include guards and are otherwise guaranteed to be unique (either contain a data/time or a guid) for this. Adding a BOOST_ prefix to those does not add anything but additional effort on behalf of library maintainers.

[pdimov]

The motivation for consistently applying a BOOST_ prefix even to unique include guards is that companies want to prepare private Boost releases (that can coexist with the official one, or with another private one) by renaming BOOST_ to f.ex. MYBOOST_.

[hkaiser]

@pdimov Thanks Peter. Makes sense.