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: creating a new local variable after a goto Date: Tue, 15 Nov 2022 16:26:12 -0800 Organization: A noiseless patient Spider Lines: 15 Message-ID: <86zgcrd9sr.fsf@linuxsc.com> References: <87zge0jumy.fsf@bsb.me.uk> <38h2L.404269$wLZ8.129177@fx18.iad> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader01.eternal-september.org; posting-host="c33488f0e6c0635625a64620cc1d5893"; logging-data="2280928"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+oDrhJSUezQbhS8R6RtORHy2fMQCKvufg=" User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux) Cancel-Lock: sha1:yYFQBQCZzzE8Tm9hiuNZqdZw8jU= sha1:uvGERrMVt4clxWOrOwiGlPzNFpg= Xref: csiph.com comp.lang.c++:87406 Richard Damon writes: > deprecated mean it MIGHT not work under some future Standard. It is > an advanced warning that it might be removed (but no promise that it > will). Deprecated does not mean the same thing as obsolescent. Declaring a construct deprecated is a statement of intent that the construct /will/ be removed at some indefinite time in the future. Declaring a construct obsolescent is meant to serve notice that the construct should be avoided if possible because it /may/ be removed at some future time.