Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: "Rod Pemberton" Newsgroups: comp.lang.forth Subject: Re: CASE mis-understanding? Date: Tue, 18 Feb 2014 18:20:31 -0500 Organization: Aioe.org NNTP Server Lines: 16 Message-ID: References: <52e54d17.461102185@news.demon.co.uk> <2014Feb15.171430@mips.complang.tuwien.ac.at> <2014Feb17.150541@mips.complang.tuwien.ac.at> <2014Feb18.103428@mips.complang.tuwien.ac.at> <2014Feb18.151937@mips.complang.tuwien.ac.at> <7xppmks7v9.fsf@ruckus.brouhaha.com> <2014Feb18.181426@mips.complang.tuwien.ac.at> <7xmwhoi4px.fsf@ruckus.brouhaha.com> NNTP-Posting-Host: CNsg4fVcCsvs3UaOgZtQCw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Opera Mail/12.16 (Linux) X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.forth:28545 On Tue, 18 Feb 2014 14:46:34 -0500, Paul Rubin wrote: > The C standard has two classes of unspecified behavior: "implementation > dependent" where the compiler writer gets to choose what semantics they > want, but then they have to stick to it consistently; and "undefined" > where consistency is not required. I would add a few more classes: 1) required contradictions in the specification 2) result of various interactions withins C 3) translation from C to assembly or binary Rod Pemberton