| ??? 05/25/12 15:43 Read: times |
#187523 - Common doesn't mean recommended Responding to: ???'s previous message |
It may be common to do this (and I've certainly seen it), but I wouldn't recommend it. I believe these sorts of techniques are hard to maintain if you didn't write the code snd this is what gives C a bad name. |
| 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 |