Reusing a name may be good or bad, e.g. macro code, copy&repeated paste of snippets of code with a variable named 'temp'.

 

But beside reusing the name, undeclaring a variable, when it is no longer needed can be good.
 

-----Ursprüngliche Nachricht-----
Von: codusnocturnus via Std-Proposals <std-proposals@lists.isocpp.org>
Gesendet: Mi 10.12.2025 02:45
Betreff: Re: [std-proposals] [PXXXXR0] Add a New Keyword `undecl`
An: std-proposals@lists.isocpp.org;
CC: codusnocturnus <codusnocturnus@protonmail.com>;
The only motivation I can discern from the paper is to reuse a name with a different type/meaning, which seems to run counter to every coding guideline I’ve ever seen.
 
It really seems like the existing solutions (using a different name, like a1 and a2, or an enclosing scope) are better in every way.

 


Sent from Proton Mail for iOS.


-------- Original Message --------
On Tuesday, 12/09/25 at 17:23 wjf via Std-Proposals <std-proposals@lists.isocpp.org> wrote:
see attachment
 
-- 
 Std-Proposals mailing list
 Std-Proposals@lists.isocpp.org
 https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals