| ??? 05/25/12 16:13 Read: times |
#187526 - well I recommend it Responding to: ???'s previous message |
I believe these sorts of techniques are hard to maintain
I do not know about "these sorts of techniques" but this technique (extern defined or not) make things a lot easier and safer to maintain e.g. changes from U8 to U16 only take place in one place and there is no way to miss "changing in the other place". Also, in the case where things are done twice I have seen differences from not entering the same at the original creation. Erik |
| Topic | Author | Date |
| const strings in C | 01/01/70 00:00 | |
| Does not compile | 01/01/70 00:00 | |
| my question was | 01/01/70 00:00 | |
| Common to play with #define EXTERN | 01/01/70 00:00 | |
| Common doesn't mean recommended | 01/01/70 00:00 | |
| well I recommend it | 01/01/70 00:00 | |
| No - not hard to maintain at all | 01/01/70 00:00 | |
| C strings | 01/01/70 00:00 | |
| Whats wrong with a header file? | 01/01/70 00:00 | |
| nothing wrong, double work | 01/01/70 00:00 | |
| It works, and has advantages | 01/01/70 00:00 | |
| I got in a total absolute magnificent mess | 01/01/70 00:00 | |
| thanks to everyone, and next question is | 01/01/70 00:00 | |
| about (tables of) pointers to const strings | 01/01/70 00:00 | |
C++ and style | 01/01/70 00:00 |