Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | Raj Pashwar <raj121190@hotmail.NOSPAM.com> |
|---|---|
| Newsgroups | comp.lang.c |
| Subject | Standard Library macros |
| Date | 2012-07-19 17:41 +0000 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <ju9gsq$5s0$1@speranza.aioe.org> (permalink) |
In another thread I was asking about declaring printf() without including <stdio.h>. I realized that one time this will fail, is when the Platform Library uses a macro for printf(). Actually this is quite likely, because printf (...) can be expanded to fprintf(stdout,...). So I got to thinking. Is there a way to tell (by preference at compile time) whether a standard-library identifier, corresponds to a macro? Cheers, Raj
Back to comp.lang.c | Previous | Next — Next in thread | Find similar | Unroll thread
Standard Library macros Raj Pashwar <raj121190@hotmail.NOSPAM.com> - 2012-07-19 17:41 +0000 Re: Standard Library macros Ben Pfaff <blp@cs.stanford.edu> - 2012-07-19 10:46 -0700 Re: Standard Library macros Ben Bacarisse <ben.usenet@bsb.me.uk> - 2012-07-19 21:35 +0100 Re: Standard Library macros Nobody <nobody@nowhere.com> - 2012-07-20 07:55 +0100
csiph-web