Macro compilation in C++

RE: Macro compilation in C++

Nguyen Hoan Hoang — Wed, 20 Dec 2017 06:40:30 GMT

You are right, I use GNU C++11 flag not the ISO C++ 11.

RE: Macro compilation in C++

Jørgen Holmefjord — Wed, 20 Dec 2017 06:24:20 GMT

This is not legal syntax in C++11 (C++20 supports it). From some answers online, it can look like GCC's C++ frontend will support this syntax for older standards as well, but this does not mean every compiler will support it.

RE: Macro compilation in C++

Nguyen Hoan Hoang — Wed, 20 Dec 2017 00:17:40 GMT

I don't have any issue compiling that in C++ see EHAL code.
Verify that you have C++ 11 setting for the compiler. PS. I am using GCC 6.2

RE: Macro compilation in C++

Jørgen Holmefjord — Tue, 19 Dec 2017 21:35:53 GMT

Hi,

Unfortunately, I do not see any way to use the macros with C++ as-is. These macros evalueate down to assignment of variables to members of a struct, like this:

NRF_SECTION_SET_ITEM_REGISTER(sdh_soc_observers, _prio, static nrf_sdh_soc_evt_observer_t _name) =  \
{                                                                                                   \
    .handler   = _handler,                                                                          \
    .p_context = _context                                                                           \
}

This format does not seem to be supported by C++ (specifying the name of the member that is being assigned). Instead, you will have to use this format:

NRF_SECTION_SET_ITEM_REGISTER(sdh_soc_observers, _prio, static nrf_sdh_soc_evt_observer_t _name) =  \
{                                                                                                   \
    _handler,                                                                          \
    _context                                                                           \
}

Note that this format is not as safe, as it will fail if you mess up the order of the assignments. I will report this issue internally, but I cannot guarantee that it will be fixed/changed. Our SDK is written to support C, and some of the coding methods is not well supported by C++.

Best regards,

Jørgen