220 3628 article Path: news.gmane.org!not-for-mail From: Tony V E Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: "break break ;" etc. to break out of nested loops Date: Mon, 8 Apr 2013 15:24:15 -0400 Lines: 94 Approved: news@gmane.org Message-ID: References: <1f964e4b-2762-43b8-85e5-41392926b07a@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c34d9aec3b5e04d9de6193 X-Trace: ger.gmane.org 1365449058 12695 80.91.229.3 (8 Apr 2013 19:24:18 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 8 Apr 2013 19:24:18 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBCUZ5QWKNQIOFMUMRMCRUBGSH7OXS@isocpp.org Mon Apr 08 21:24:22 2013 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-lb0-f200.google.com ([209.85.217.200]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UPHfv-0002kx-Eg for gclcip-std-proposals@m.gmane.org; Mon, 08 Apr 2013 21:24:19 +0200 Original-Received: by mail-lb0-f200.google.com with SMTP id t12sf8941748lbi.11 for ; Mon, 08 Apr 2013 12:24:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:x-beenthere:x-received:received-spf:mime-version :x-received:in-reply-to:references:date:message-id:subject:from:to :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:x-google-group-id:list-post :list-help:list-archive:list-subscribe:list-unsubscribe:content-type; bh=Ge2iNsJfF3Ubf/8ew21vYycG+vksmoSIkiGldpdz5Kg=; b=ZQJPaQI/j6OCINSOe/76H04PVVT+a+4ghwElrWXLalxMKxzXDYRzNAyEFkiT+bWn8j qp6/TDAESWM785zmWbNelFTr6chEKQaDhAVdbv8TbCV/hKM7TE+zbGqKhln3wGAuc78D 6405EjSxj3celnkGzq5noWbfobKdxLbzqEDnBcT4BeqIHF1BsEFEHKH4pe+Rp6hCZ9SF OfyqHmlUplMbpqUbryiVNN39weiLFOnWsetT8jxktd+4AePBLTLcoTQrcMybkhbbgj6B sxN1cW4+3hsg/xKGWcmEI//25sxCZWyZHFy1J88gN7C6d9thzwVVEECZKDY+YA0ZQ5Yp X-Received: by 10.112.19.132 with SMTP id f4mr1234609lbe.3.1365449058704; Mon, 08 Apr 2013 12:24:18 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.152.29.199 with SMTP id m7ls252320lah.94.gmail; Mon, 08 Apr 2013 12:24:17 -0700 (PDT) X-Received: by 10.112.170.7 with SMTP id ai7mr12322474lbc.42.1365449056867; Mon, 08 Apr 2013 12:24:16 -0700 (PDT) Original-Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [2a00:1450:4010:c03::229]) by mx.google.com with ESMTPS id sk2si9122908lbb.283.2013.04.08.12.24.15 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Apr 2013 12:24:15 -0700 (PDT) Received-SPF: pass (google.com: domain of tvaneerd@gmail.com designates 2a00:1450:4010:c03::229 as permitted sender) client-ip=2a00:1450:4010:c03::229; Original-Received: by mail-la0-f41.google.com with SMTP id er20so607863lab.28 for ; Mon, 08 Apr 2013 12:24:15 -0700 (PDT) X-Received: by 10.152.87.73 with SMTP id v9mr12545710laz.2.1365449055677; Mon, 08 Apr 2013 12:24:15 -0700 (PDT) Original-Received: by 10.112.83.103 with HTTP; Mon, 8 Apr 2013 12:24:15 -0700 (PDT) In-Reply-To: X-Original-Sender: tvaneerd@gmail.com X-Original-Authentication-Results: mx.google.com; spf=pass (google.com: domain of tvaneerd@gmail.com designates 2a00:1450:4010:c03::229 as permitted sender) smtp.mail=tvaneerd@gmail.com; dkim=pass header.i=@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:3628 Archived-At: --001a11c34d9aec3b5e04d9de6193 Content-Type: text/plain; charset=ISO-8859-1 > label: for (;;) > > { > > break label; > > } > > > > > > And all that is not saying I agree with any of it, or really want it; > just some suggestions. > > I think I would prefer > > for outer (...) { > for (...) { > if (...) > break outer; > } > } > > Using a label to refer to its labeled statement feels like an abuse of the > facility to me. > You would think that using a label to refer to the statement it labels would make complete sense :-), but I actually completely agree with you (I suspect the C++ term 'label' has lost much of its similarity with the actual English word over the years); and I would prefer your style (if we were to ever do something like this). Tony -- --- 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. Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/?hl=en. --001a11c34d9aec3b5e04d9de6193 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
> label: for (;;)

> {
> =A0=A0 break label;
> }
>
>
> And all that is not saying I agree with any of it, or really want it; = just some suggestions.

I think I would prefer

for outer (...) {
=A0 for (...) {
=A0=A0=A0 if (...)
=A0=A0=A0=A0=A0 break outer;
=A0 }
}

Using a label to refer to its labeled statement feels like a= n abuse of the facility to me.


You woul= d think that using a label to refer to the statement it labels would make c= omplete sense :-), but I actually completely agree with you (I suspect the= C++ term 'label' has lost much of its similarity with the actual E= nglish word over the years);=A0 and I would prefer your style (if we were t= o ever do something like this).

Tony

--
 
---
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.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-pro= posals/?hl=3Den.
 
 
--001a11c34d9aec3b5e04d9de6193-- .