??? 07/26/04 10:35 Read: times |
#74872 - RE: Nothing 8051-specific here Responding to: ???'s previous message |
nothing is sure but compilers for embedded systems often include it
anyway the sequence #define true 0==0 #define false 0==1 typedef unsigned char byte; typedef unsigned int__8 (or 16 or 32 or 64) WORD; typedef unsigned int__16 DWORD; could be useful and just clarify the code i love the typedef register unsigned char whatyouwant (for 8 bit use) i believe not many compiler accept it |
Topic | Author | Date |
doub about strutc pointers | 01/01/70 00:00 | |
RE: doub about strutc pointers | 01/01/70 00:00 | |
RE: doub about strutc pointers | 01/01/70 00:00 | |
What do you doubt? | 01/01/70 00:00 | |
RE: What do you doubt? | 01/01/70 00:00 | |
RE: What do you doubt? | 01/01/70 00:00 | |
RE: What do you doubt? | 01/01/70 00:00 | |
RE: What do you doubt? | 01/01/70 00:00 | |
RE: What do you doubt? | 01/01/70 00:00 | |
RE: What do you doubt? | 01/01/70 00:00 | |
RE: What do you doubt? | 01/01/70 00:00 | |
RE: undefined behaviour land | 01/01/70 00:00 | |
RE: What do you doubt? | 01/01/70 00:00 | |
Still unknown doubt | 01/01/70 00:00 | |
RE: doub about strutc pointers | 01/01/70 00:00 | |
Nothing 8051-specific here | 01/01/70 00:00 | |
RE: Nothing 8051-specific here | 01/01/70 00:00 | |
RE: doub about strutc pointers | 01/01/70 00:00 | |
RE: doub about strutc pointers![]() | 01/01/70 00:00 |