27 Feb
2017
27 Feb
'17
4:01 p.m.
On 02/27/17 17:07, Peter Dimov via Boost wrote:
Groke, Paul wrote: ...
One way to fix this would obviously be to introduce two additional macros, e.g. BOOST_ALIGNMENT_DECLSPEC and BOOST_ALIGNMENT_ATTRIBUTE.
...
Another option would be a BOOST_ALIGNED_VARIABLE(alignment, variable_definition) macro.
...
The third option I can think of would be to leave things as they are, which of course would mean that I can't submit my Boost.Atomic implementation for z/OS... hm.
The obvious fourth option is to just #ifdef here for z/OS.
BOOST_ALIGNMENT is used in quite a few places, including outside Boost.Atomic. Adding preprocessor checks everywhere would be messy.