| ??? 12/05/11 21:29 Read: times |
#185021 - That's the problem... Responding to: ???'s previous message |
Matthias Arndt said:
in a context of a 8051 MCU, I’d rather introduce my own data type for pointers anyway due to the different possible memory spaces.
Exactly! As already mentioned, doing 'C' on an 8051 requires some very specific extensions to the language - so it's hard to come up with a universally appropriate stdint.h Matthias Arndt said:
#define _Bool bit #define BOOL bit #define bool _Bool #define __bool_true_false_are_defined 1 But there are specific restrictions on the bit type - so you might not always want to have BOOL as just a synonym for bit... These are probably a good reasons for Keil not to provide a stdint.h with their C51... |
| Topic | Author | Date |
| stdint.h for Keil C? | 01/01/70 00:00 | |
| ! StdInt.h | 01/01/70 00:00 | |
| Make one | 01/01/70 00:00 | |
| Ofcourse | 01/01/70 00:00 | |
| SDCC's headers can be adapted | 01/01/70 00:00 | |
That's the problem... | 01/01/70 00:00 | |
| So just write one! | 01/01/70 00:00 | |
| Does Keil claim C99 compliance at all? | 01/01/70 00:00 | |
| They have a statement on this... | 01/01/70 00:00 | |
| C90 conformance - not C99. | 01/01/70 00:00 | |
| I personally don't need full C99 compliance | 01/01/70 00:00 | |
| Yes possible. But maybe not economical. | 01/01/70 00:00 | |
| Not difficult | 01/01/70 00:00 |