Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
Andy Neil
12/05/11 14:29
Read: 672 times

#185021 - That's the problem...
Responding to: Matthias Arndt's previous message
Matthias Arndt said:
in a context of a 8051 MCU, Id rather introduce my own data type for pointers anyway due to the different possible memory spaces.


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...

List of 13 messages in thread
stdint.h for Keil C?      Matthias Arndt      12/03/11 11:38      
   ! StdInt.h      Michael Karas      12/03/11 12:42      
      Make one        Per Westermark      12/03/11 15:11      
         Ofcourse      Matthias Arndt      12/04/11 01:51      
            SDCC's headers can be adapted      Matthias Arndt      12/04/11 02:25      
               That's the problem...      Andy Neil      12/05/11 14:29      
   So just write one!      Andy Neil      12/03/11 17:05      
   Does Keil claim C99 compliance at all?      Jan Waclawek      12/04/11 01:45      
      They have a statement on this...      Matthias Arndt      12/04/11 02:21      
         C90 conformance - not C99.      Per Westermark      12/04/11 05:32      
            I personally don't need full C99 compliance      Matthias Arndt      12/04/11 08:09      
               Yes possible. But maybe not economical.      Per Westermark      12/04/11 09:06      
               Not difficult      Andy Neil      12/04/11 14:36      

Back to Subject List