Path: csiph.com!news.mixmin.net!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Tim Rentsch Newsgroups: comp.lang.c Subject: Re: Christmas Quiz 2022 Date: Sun, 18 Dec 2022 17:02:44 -0800 Organization: A noiseless patient Spider Lines: 16 Message-ID: <865ye82ojv.fsf@linuxsc.com> References: <87zgbkxv8n.fsf@bsb.me.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader01.eternal-september.org; posting-host="ff406b04d09b824d6c1109f51ef0323b"; logging-data="102999"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX184svPm/3HUqB0313llL0bx1A3BGW0eIV8=" User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux) Cancel-Lock: sha1:pDXFLSLfV9zhlBerEGPZz172/gg= sha1:au8XMCiipQyvp1q0xyBgvI+mXZE= Xref: csiph.com comp.lang.c:168587 Ben Bacarisse writes: > Roman P writes: > >> 3) What happens when you overflow an int variable, that is, set it >> to a value beyond its range? > > And here there is even more ambiguity since a variable (what might > better be called a named object) can be set in two ways, and the C > standard says different things about each! I don't know what you're getting at here. ISTM that there is basically only one way of setting a variable (or named object if you will), in the sense that different ways of "setting a variable" all reduce to the same semantics (not counting things like memcpy(), unions, etc). What am I missing?