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: Is 'extern' necessary? Date: Tue, 14 Feb 2017 08:51:33 -0800 Organization: None to speak of Lines: 28 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="224226333e9535e2f06996e59b2311d1"; logging-data="29040"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX192OalA6McHlviwrOhTYu3K" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:DWTtIkoQvJORjIbzIhEJYnwlVZU= sha1:YACtYzGsAnShoW1KsN6GSdBfQLA= Xref: csiph.com comp.lang.c:103886 BartC writes: > On 14/02/2017 08:28, David Brown wrote: [...] >> Standard library code is part of the implementation. Even if it is >> developed separately from the compiler, it is still in close cooperation >> with the compiler. > > "The" compiler? I thought such libraries were completely independent > from any one compiler and were all interchangable? What gave you that idea? > Or you finally admitting that perhaps the MingW library /is/ really > designed to work with gcc? "finally admitting"? Of course it is. MinGW is an implementation that include gcc as its compiler. The library component of MinGW is, as far as I know, intended to work with gcc, and only with gcc. Has anyone claimed otherwise? [...] -- 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"