Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: Even more problems with lcc-win Date: Sat, 25 Mar 2017 13:43:05 -0700 Organization: None to speak of Lines: 17 Message-ID: References: <87vaqyvqzb.fsf@bsb.me.uk> <0tobdc58n3gburqbov5pafpks4rhpq3fcl@4ax.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="8a7136a2a556fadb85eac0a5973ae8a0"; logging-data="6916"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/27l5znqLYxStMVunMkiKG" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:t1UmrCrb4ikT/XBmgjPx1B5Ndps= sha1:9azH9FWLLbu15MJxJlQIDENK9qU= Xref: csiph.com comp.lang.c:107070 BartC writes: [...] > Maybe that makes a difference. But for how many decades has getc been a > macro just for this purpose? Has gcc only just got round to it? gcc doesn't provide getc. If you're on Windows, you're probably using a different library implementation than is commonly used on Linux. The compiler sees a call to getc(), and it generates code for it in accordance with the declaration (as a function, as an inline function, or as a macro) it sees in . -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"