Array with different data types

Hi everyone,

I have a int16_t array that holds some data. Now, I want to add a new element that is type of uint32. How can I added in the array?

Code:

---

int16_t m_array[] = {
      s_accel.x, s_accel.y, s_accel.z,
      s_gyro.x, s_gyro.y, s_gyro.z,
      bmm150.data.x, bmm150.data.y, bmm150.data.z,
      ADC_RawData[0], ADC_RawData[1], ADC_RawData[2], ADC_RawData[3],
      ADC_RawData[4], ADC_RawData[5], ADC_RawData[6], ADC_RawData[7]};

---

Thanks
Nick

In an array all values must have the same type.
You could create an array of uint32_t and store uint32_t in it.

It has to be on the same array since this is payload I have to transmit. The same applyies for signed and unsigned? I am considering to shift bitwise, something like this:

Code:

---


uint32 counter++;
uint16 MSB =  counter>>16;
uint16 LSB =  counter;

---

Can I have uint16 into an int16 array?

It looks like you need an array of a struct to hold the information.The struct would have variables of the correct types for your data.

Quote:

---

Originally Posted by Nikosant03

Hi everyone,

I have a int16_t array that holds some data. Now, I want to add a new element that is type of uint32. How can I added in the array?

Code:

---

int16_t m_array[] = {
      s_accel.x, s_accel.y, s_accel.z,
      s_gyro.x, s_gyro.y, s_gyro.z,
      bmm150.data.x, bmm150.data.y, bmm150.data.z,
      ADC_RawData[0], ADC_RawData[1], ADC_RawData[2], ADC_RawData[3],
      ADC_RawData[4], ADC_RawData[5], ADC_RawData[6], ADC_RawData[7]};

---

Thanks
Nick

---

C doesn't allow for mixed type arrays. In C, arrays are always arranged with the elements consecutive in memory. So all elements have to be of the same size. In fact they also have to be of the same type. Other languages like Javascript allow for mixed type arrays, but the underlying data structures are higher level.

There's no good way to achieve what you want to do. You could use a wider element type, but because the int16_t's are signed whilst the uint32_t's are unsigned, this means going to 64 bits. You could us a union with a "type" field, but that is very awkward and inefficient.

Best thing is to rewrite the program so data is not held in one array.

> It has to be on the same array since this is payload I have to transmit.
Transmit where (and how)?

Network send() for example won't care whether it's one buffer or two, if you decide to send the uint16 in one buffer and the uint32 in another.


Serialization - Wikipedia
You normally separate your internal storage representation from your external transmission format.

While everything was a uint16, everything was peachy.
The first chink in the armour was the uint32, and then it's going to get messy if you also want to send a string.