MSP430F5529: Old school (unsigned int) vs (uint16_t) Errors

Andy Delle

Prodigy 230 points

Part Number: MSP430F5529

Tool/software:

When pulling in code from GitHub CCS chokes on the modern C type definitions such as unit16_t.

If I change the type definition to legacy unsigned int, it compiles.

same for uint8_t or int8_t, = unsigned char, char

As CSS is a modern compiler, why does it not accept the modern C type definitions?

over 1 year ago

+1 Keith Barkley over 1 year ago

Guru 42145 points

It does if you include stdint.h.

I assume you mean uint16_t not unit16_t.

+1 David Schultz over 1 year ago

Guru 24915 points

Because those type definitions live in the file stdint.h

0 Keith Barkley over 1 year ago

Guru 42145 points

I am not sure what you mean by "modern", but my 5th edition of Harbison and Steele describes this header in C99. 8^)

+1 Andy Delle over 1 year ago in reply to Keith Barkley

Prodigy 230 points

I learned C on my own around 1986 with the K&R book. My formal education 1978-1982 was assembly and Fortran. C was not really used much back then.

For the young folks, K&R means Kernighan and Ritchie, the inventors of the C language at Bell Labs in the 70s. The development compiler was named B, but once the bugs were worked out it became C.

0 Keith Barkley over 1 year ago in reply to Andy Delle

Guru 42145 points

Not exactly, B was a simplified language based on BCPL, and C added types and some other additions. The joke is that "C" is the letter that follows "B" and that C++ should have been named "P".

**Attention** This is a public forum

MSP low-power microcontrollers

MSP low-power microcontroller forum

MSP430F5529: Old school (unsigned int) vs (uint16_t) Errors