Posted by jimfred on 2015-12-16 01:11

I use this in OpenStm32 and with other toolsets:

See this for more info.

Posted by spflanze on 2015-12-16 01:21

How are you able to get the compiler to accept the sizeof operator in your macro? When I do it I get these errors:

invalid application of ‘sizeof’ to incomplete type ‘const float[]’
invalid application of ‘sizeof’ to incomplete type ‘const uint16_t[]’
invalid application of ‘sizeof’ to incomplete type ‘const uint32_t[]’

Posted by jimfred on 2015-12-16 14:19

The storage size of a float[] would be unknown to the compiler.

I wonder if you’re passing a statically allocated array into a function with a ‘const float[]’ arguement. If so, then, you’re right - that macro would not work in the context of that function. The function could be getting an array of any size and the compiler wouldn’t be able to resolve the size of the array in the context of the function.

Some options:

• Have that function reference the statically allocated array directly
• Add an array size parameter to the function arguement list
• Create (or re-use) a class that knows the size
• Create a template with a size

Posted by spflanze on 2015-12-16 18:42

I have figured out why the compiler does not accept this. The array is global. Its size and initialization is done in a .c file other than the one this error appears in. It is not sufficient that a header be used to externally declare it. The size and initialization would have to be done in the header, but doing that has caused other problems. I am giving up on doing it this way. I am going to have to define a size variable in the .c file in the next line after the array is defined. For example:

int arr[] = { 1, 2, 3, 4, 5 };
size_t arr_N = sizeof(arr)/sizeof(*arr);

This is the only way to be sure the compiler knows the size of the array in advance of using the sizeof operator.

There is no advantage to using the above NUMSIZE macro over the sizeof operator. That NUMSIZE macro will work only where the sizeof operator works.

In my application I am not going to need the overload checking your COUNT_OF(x) macro provides because I am working only in C, not C++. I can see how it can be useful in C++ though.