220 31921 article Path: news.gmane.org!.POSTED!not-for-mail From: Richard Smith Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: This variable should not be named: an identifier (not) to remember Date: Sat, 1 Apr 2017 21:19:37 -0700 Lines: 108 Approved: news@gmane.org Message-ID: References: <985b9b2a-c734-45eb-95f4-db4dc0d309a1@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a114423f6ddf90f054c275944 X-Trace: blaine.gmane.org 1491106790 10465 195.159.176.226 (2 Apr 2017 04:19:50 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 2 Apr 2017 04:19:50 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBDVNBJG4YAIBBW7XQHDQKGQEQMWDO7Q@isocpp.org Sun Apr 02 06:19:43 2017 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-lf0-f69.google.com ([209.85.215.69]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cuWzG-00016p-J6 for gclcip-std-proposals@m.gmane.org; Sun, 02 Apr 2017 06:19:34 +0200 Original-Received: by mail-lf0-f69.google.com with SMTP id q141sf423741lfe.13 for ; Sat, 01 Apr 2017 21:19:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=urW2QZwmcJ/cx8jT/g4d5zAFEqFBriZRbC1JMvk+CZo=; b=P6Gyh36zd2kImV+bPICeh/HlacPW1bSXqtgvghFvTd7u+4vRR9IVjumS2p7sBnVCG+ 2ngEaA4zjM3rQE+6ctiIw9n+qY8Cr5DT5QhZnt2seg4Hx2zrBM8jMEnuDB7Q7xBeVW5B xSs6RPA8SaOdvgT12OWjyJgzVTKNtIUjxIf8J9lJBXAk1L8UOQ9ywur0D+9+nVa0fFQK S9lP5PXtVXiIbrcVsWB4m50dqzShvU7x373Bs5k4049QjM3+Wt1vNc5PUx8vyq7KEeqQ J4eZeGqvQqfgW/RAJPFlH25DriR4l2ISMJMgjqWNE4n3U5gt6tgFrgjiu+swx999mymr mjzA== X-Gm-Message-State: AFeK/H1QRGN46jMme2oo61sM45so07dt9YcrtvA7IxrGfjZ/eKseH/8gxv+Qk2QB2H9l9g== X-Received: by 10.25.169.141 with SMTP id s135mr1447806lfe.30.1491106780514; Sat, 01 Apr 2017 21:19:40 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.28.113.194 with SMTP id d63ls344970wmi.11.gmail; Sat, 01 Apr 2017 21:19:39 -0700 (PDT) X-Received: by 10.28.8.147 with SMTP id 141mr4319597wmi.43.1491106779187; Sat, 01 Apr 2017 21:19:39 -0700 (PDT) Original-Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com. [2a00:1450:400c:c09::231]) by mx.google.com with ESMTPS id h7si9926014wma.43.2017.04.01.21.19.39 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 01 Apr 2017 21:19:39 -0700 (PDT) Received-SPF: pass (google.com: domain of metafoo@gmail.com designates 2a00:1450:400c:c09::231 as permitted sender) client-ip=2a00:1450:400c:c09::231; Original-Received: by mail-wm0-x231.google.com with SMTP id t189so25387323wmt.1 for ; Sat, 01 Apr 2017 21:19:39 -0700 (PDT) X-Received: by 10.28.175.129 with SMTP id y123mr4196064wme.67.1491106778705; Sat, 01 Apr 2017 21:19:38 -0700 (PDT) Original-Sender: metafoo@gmail.com Original-Received: by 10.80.148.82 with HTTP; Sat, 1 Apr 2017 21:19:37 -0700 (PDT) Original-Received: by 10.80.148.82 with HTTP; Sat, 1 Apr 2017 21:19:37 -0700 (PDT) In-Reply-To: <985b9b2a-c734-45eb-95f4-db4dc0d309a1@isocpp.org> X-Original-Sender: richard@metafoo.co.uk X-Original-Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com; spf=pass (google.com: domain of metafoo@gmail.com designates 2a00:1450:400c:c09::231 as permitted sender) smtp.mailfrom=metafoo@gmail.com Precedence: list Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org List-ID: X-Google-Group-Id: 399137483710 List-Post: , List-Help: , List-Archive: List-Subscribe: , List-Unsubscribe: , Xref: news.gmane.org gmane.comp.lang.c++.isocpp.proposals:31921 Archived-At: --001a114423f6ddf90f054c275944 Content-Type: text/plain; charset=UTF-8 I don't think you need a reserved identifier for this, nor to change the meaning of any existing code (whether or not it uses a reserved identifier). It seems to me that your use cases could be addressed by allowing the identifier _ to declare multiple entities within a block scope. (If it is multiply declared, any reference to it would be ill-formed due to ambiguity; if it's only declared once, it can still be referenced for backwards compatibility, but such usage could be deprecated.) Have you considered that possibility? It would give a better name (_ rather than __) and avoid "breaking" existing code that uses __. On 27 Mar 2017 10:27 am, "Alberto Barbati" wrote: Hello, this is a draft for a proposal to add a special meaning to the identifier __ (double underscore) so that it can be used (even repeatedly in the same lexical scope) for all variables whose name is not important and that is no longer needed after declaration. The draft includes a few examples. Is there any interest in this? Thanks in advance, Alberto -- You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group. To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org. To post to this group, send email to std-proposals@isocpp.org. To view this discussion on the web visit https://groups.google.com/a/ isocpp.org/d/msgid/std-proposals/985b9b2a-c734-45eb- 95f4-db4dc0d309a1%40isocpp.org .. -- You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group. To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org. To post to this group, send email to std-proposals@isocpp.org. To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CAOfiQqnfaqA4YhpNphKg4oPPAMNOe7vPjqxqLvA-EnGjk-pVEA%40mail.gmail.com. --001a114423f6ddf90f054c275944 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I don't think you need a reserved identifier for= this, nor to change the meaning of any existing code (whether or not it us= es a reserved identifier). It seems to me that your use cases could be addr= essed by allowing the identifier _ to declare multiple entities within a bl= ock scope. (If it is multiply declared, any reference to it would be ill-fo= rmed due to ambiguity; if it's only declared once, it can still be refe= renced for backwards compatibility, but such usage could be deprecated.)

Have you considered that possibility? It would give a bette= r name (_ rather than __) and avoid "breaking" existing code that= uses __.

On= 27 Mar 2017 10:27 am, "Alberto Barbati" <albertobarbati@gmail.com> wrote:
Hello,

this i= s a draft for a proposal to add a special meaning to the identifier __ (dou= ble underscore) so that it can be used (even repeatedly in the same lexical= scope) for all variables whose name is not important and that is no longer= needed after declaration. The draft includes a few examples.

Is the= re any interest in this?

Thanks in advance,

Alberto

--
You received this message because you are subscribed to the Google Groups &= quot;ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit = https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/985b= 9b2a-c734-45eb-95f4-db4dc0d309a1%40isocpp.org.

--
You received this message because you are subscribed to the Google Groups &= quot;ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to std-proposa= ls+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit htt= ps://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CAOfiQqnfaqA4YhpN= phKg4oPPAMNOe7vPjqxqLvA-EnGjk-pVEA%40mail.gmail.com.
--001a114423f6ddf90f054c275944-- .