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: Compiler design in C? Date: Sat, 12 Nov 2016 14:28:36 -0800 Organization: None to speak of Lines: 16 Message-ID: References: <87shr14n5b.fsf@gmail.com> <87r36k1l4w.fsf@gmail.com> <3e47c9bc-1c0a-40dc-9dc3-92e88ace6c31@googlegroups.com> <23d0f58e-a17c-4ef7-8db6-9cc5b7bcaf04@googlegroups.com> <9e27a17d-aaab-48e1-9139-95114dea0da6@googlegroups.com> <3121b7be-aca1-44b0-9dc9-6b23611bbfba@googlegroups.com> <300e8fda-56cf-476f-9bd7-257791357090@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="f830fb76aec43d91603702f100a3d579"; logging-data="24495"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19PsfzysVmIClbIUcZAssIW" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:tQYevG+6D9mz0kZGUt9N+ZWH59A= sha1:EJO+Qk18CLX1btwlmB+VcgCk0hw= Xref: csiph.com comp.lang.c:96437 supercat writes: [...] > What I have called for would be standard conventions via which programmers > could indicate what features and guarantees they require, and ensure that > an attempt to process the program with an incompatible implementation would > be rejected outright rather than yielding unreliable behavior. [...] Let me encourage you to write up a coherent specification for what you're proposing and make it available somewhere on the web. -- 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"