"Paul Mensonides" <pmenso57@comcast.net> writes:
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Aleksey Gurtovoy
One thing that we really have to take care of before branching is long filenames. Could maintainers of the following libraries please fix the corresponding problems listed in detail in http://www.boost.org/regression-logs/inspection_report.html?
preprocessor
libs/preprocessor/doc/blank.html: unlinked file
Fixed.
libs/preprocessor/doc/headers/enum_params_with_a_default.hpp.html: filename > 31 chars libs/preprocessor/doc/headers/enum_params_with_defaults.hpp.html: filename > 31 chars libs/preprocessor/doc/headers/repetition/enum_params_with_a_default.hpp.html: filename > 31 chars libs/preprocessor/doc/headers/repetition/enum_params_with_defaults.hpp.html: filename > 31 chars
libs/preprocessor/doc/headers/repetition/enum_trailing_binary_params.hpp.html: filename > 31 chars
libs/preprocessor/doc/ref/enum_trailing_binary_params.html: filename > 31 chars libs/preprocessor/doc/ref/enum_trailing_binary_params_z.html: filename > 31 chars
Fixed with comment. The 31+ filename limit breaks the naming convention where filenames mirror their contained facilities. This is particularly a problem with the pp-lib since there are no namespaces that can be mirrored with directory structure.
Yeah, that's really a shame... oh, but these are all html files, no? If so I don't think that's so terrible. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com