I wonder why a standard C term #undef
isn't explicitly documented comparing to #define
which is explained:
Is it unsupported or what else? By mistake?
I wonder why a standard C term #undef
isn't explicitly documented comparing to #define
which is explained:
Is it unsupported or what else? By mistake?
Because the docs are an overview of things that an inexperienced programmer might want to know. They do not cover all the intricacies of C/C++.
shkaff:
I wonder why a standard C term#undef
isn't explicitly documented comparing to#define
which is explained:Is it unsupported or what else? By mistake?
See Index of Directives (The C Preprocessor) and the parent pages.
What am I missing here? To my mind this is a simple software question about #undef . No change to the Arduino project has been proposed and none is required. #undef is a command within the C pre-processor (cpp) which has been in cpp for as long as I can remember and I have been using cpp for 30 odd years.
This should be moved back to to where it belongs - the "Programming Questions" forum.
I don't see it as a programming question. It is asking why documentation of #undef does not exist on the reference pages whereas #define does.
Pete
In which case it needs to be raised as an Arduino documentation bug and not just left to fester here.
I have just tried the #undef because I have a need to use a variation of the servo library for a single servo but require an interrupt driven timer for a model clock. So though simple: undefined _useTimer5, which will then allow me to define my own ISR for timer5.
Good idea while it lasted! It doesn't work so appears not to be supported.
It doesn't work so appears not to be supported.
Works for me.