Path: csiph.com!xmission!nnrp.xmission!.POSTED.shell.xmission.com!not-for-mail From: nobody@example.org (Scott) Newsgroups: comp.lang.c Subject: Re: Question about #error Date: Sun, 07 Apr 2019 17:10:59 GMT Organization: XMission http://xmission.com/ Message-ID: <5caa2e4f.1731781783@core> References: <5c9c4cbb.822065408@core> <86o95il20y.fsf@mailhub.linuxsc.com> Injection-Info: news.xmission.com; posting-host="shell.xmission.com:2607:fa18:0:beef::4"; logging-data="9319"; mail-complaints-to="abuse@xmission.com" X-Newsreader: Forte Free Agent 1.21/32.243 Xref: csiph.com comp.lang.c:142888 On Sun, 7 Apr 2019 10:22:55 -0000 (UTC), gazelle@shell.xmission.com (Kenny McCormack) wrote: >In article <86o95il20y.fsf@mailhub.linuxsc.com>, >Tim Rentsch wrote: >... >>> I wonder if there's a compiler flag to have it regard #error as an >>> immediate halting point. I don't wonder enough to look it up though. >> >>I believe there is not, at least for gcc. In practice >>though I expect the following would have the desired >>effect: >> >> #error ... your message here ... >> #include "no-such-file-so-stop-compiling-already.h" >> > >This is a good suggestion - and, really nice that this thread finally got >back on-topic after all the ranting and raving about other stuff that many >posters have engaged in. I will try it out at some point. Thanks. That *is* a good hint. Clever. With my luck, "no-such-file-so-stop-compiling-already.h" would actually exist as some kind of dummy load for compression or encryption experiments. The chances of it containing valid C are low, though.