??? 11/17/08 20:00 Read: times |
#160098 - The preprocessor is often a good friend Responding to: ???'s previous message |
Yes. It always helps to keep down the number of compiler-specific or target-specific source code lines.
One day, the used compiler may stop being supported for the required target... Many C++ purists likes to drop the preprocessor. But it is very valuable to have in both C and C++ to "normalize" source code. Just as long as it doesn't try too hard, so the user just sees #defined symbols everywhere without being able to understand the underlying "magic". |
Topic | Author | Date |
SDCC declaring SFR bits | 01/01/70 00:00 | |
Manual | 01/01/70 00:00 | |
SDCC declaring SFR bits | 01/01/70 00:00 | |
Header files? | 01/01/70 00:00 | |
Header files? | 01/01/70 00:00 | |
The manual is not enough! | 01/01/70 00:00 | |
This is one way | 01/01/70 00:00 | |
That's not what the manual says | 01/01/70 00:00 | |
Those SFR definitions are working | 01/01/70 00:00 | |
Need someone who knows SDCC: Maarten Brock? | 01/01/70 00:00 | |
variant syntax of SDCC keywords and ANSI-C compatibility | 01/01/70 00:00 | |
C standard compliance | 01/01/70 00:00 | |
Common for all compilers | 01/01/70 00:00 | |
coders should think twice | 01/01/70 00:00 | |
The preprocessor is often a good friend | 01/01/70 00:00 | |
Suggestion | 01/01/70 00:00 | |
thanks, but...![]() | 01/01/70 00:00 |