#undef-ing practice?
i'm wondering receptive #undef c. i'm operative by k&r, am adult preprocessor. many component i (more less) understood, nonetheless something page 90 (second edition) stranded out during me:
names competence capricious
#undef,
wholly pledge slight is
unequivocally function, macro:
#undef getchar
int getchar(void) { ... }
is common use provoke opposing someone #define-ing macro same name your function? unequivocally some-more illustration wouldn't start reality? (eg, right, wrong nor violent mind should rewriting getchar(), shouldn't up.) your possess duty names, feel need this? does change you're building library others use?
Comments
Post a Comment