| ??? 11/02/09 16:02 Read: times |
#170353 - poor choice of names Responding to: ???'s previous message |
Robert Revens said:
typedef unsigned int tWord;
typedef unsigned long tLong; As has been noted many times before, these are not terribly good choices for names - since the size (and signedness) of a "Word" is ambiguous; if you're going to define your own "portable" types, you really should give then names that explicitly state both size & signedness... |
| Topic | Author | Date |
| Odd calculation result... | 01/01/70 00:00 | |
| Hmm. Even odder. | 01/01/70 00:00 | |
| what is the definition... | 01/01/70 00:00 | |
| Compiler reuses registers and memory cells | 01/01/70 00:00 | |
| Ah. | 01/01/70 00:00 | |
| Disable compiler optimizations. | 01/01/70 00:00 | |
| Compiler bug? | 01/01/70 00:00 | |
| Maturity of compilers | 01/01/70 00:00 | |
| the primary suspect should always be the end user. | 01/01/70 00:00 | |
| "innovation" as alternative name for bug | 01/01/70 00:00 | |
| C51 also does that! | 01/01/70 00:00 | |
| C51 has smart linker | 01/01/70 00:00 | |
| I found a some genuine compiler bugs. | 01/01/70 00:00 | |
| Broken code in RTL is the worst | 01/01/70 00:00 | |
| Thanks! | 01/01/70 00:00 | |
| Defs | 01/01/70 00:00 | |
| poor choice of names | 01/01/70 00:00 | |
| Good data types are really critical | 01/01/70 00:00 | |
| I'm an idiot. | 01/01/70 00:00 | |
| informative! | 01/01/70 00:00 | |
| "Answer is wrong" | 01/01/70 00:00 | |
Which one would you prefer?? | 01/01/70 00:00 |