Opened 12 years ago
Closed 12 years ago
#5396 closed Bugs (invalid)
multi_index_container initialization in wrong order
| Reported by: | anonymous | Owned by: | Joaquín M López Muñoz |
|---|---|---|---|
| Milestone: | To Be Determined | Component: | multi_index |
| Version: | Boost 1.47.0 | Severity: | Showstopper |
| Keywords: | Cc: |
Description
On some compilers (armcc) this is at least a warning, and in our build environment, warnings are errors. There seems to be no easy workaround to get this to compile
"../../boost/multi_index_container.hpp", line 193: Error: #1299-D: members and base-classes will be initialized in declaration order, not in member initialisation list order
super(args_list,bfm_allocator::member),
"../../boost/multi_index_container.hpp", line 201: Error: #1299-D: members and base-classes will be initialized in declaration order, not in member initialisation list order
super(ctor_args_list(),bfm_allocator::member),
"../../boost/multi_index_container.hpp", line 228: Error: #1299-D: members and base-classes will be initialized in declaration order, not in member initialisation list order
super(args_list,bfm_allocator::member),
"../../boost/multi_index_container.hpp", line 249: Error: #1299-D: members and base-classes will be initialized in declaration order, not in member initialisation list order
super(x),
Hello,
I've checked the offending lines and initialization coincides with declaration order in all cases, so I'm afraid this is a problem with your compiler. Can't you suppress warnings on a per-case basis so as to ignore this one?
Closing the report as a non-bug.