220 3592 <7f30e072-ca11-4eaa-9ad0-9a1ea87106e2@isocpp.org> article Path: news.gmane.org!not-for-mail From: Benjamin Lindley Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: "break break ;" etc. to break out of nested loops Date: Sat, 6 Apr 2013 05:57:52 -0700 (PDT) Lines: 59 Approved: news@gmane.org Message-ID: <7f30e072-ca11-4eaa-9ad0-9a1ea87106e2@isocpp.org> 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="----=_Part_25_3558348.1365253072562" X-Trace: ger.gmane.org 1365270737 17101 80.91.229.3 (6 Apr 2013 17:52:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 6 Apr 2013 17:52:17 +0000 (UTC) Cc: temptony@freemail.hu To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBDI7THWOWMDRBUVXQCFQKGQECO23SCY@isocpp.org Sat Apr 06 19:52:17 2013 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-gh0-f199.google.com ([209.85.160.199]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UOWdj-0000YZ-5S for gclcip-std-proposals@m.gmane.org; Sat, 06 Apr 2013 19:10:55 +0200 Original-Received: by mail-gh0-f199.google.com with SMTP id r16sf6306432ghr.6 for ; Sat, 06 Apr 2013 10:10:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:x-beenthere:x-received:date:from:to:cc:message-id :in-reply-to:references:subject:mime-version:x-original-sender :reply-to:precedence:mailing-list:list-id:x-google-group-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe :content-type; bh=sA7dmFbJh5rkkI2/5jFiAmWfJFoZJEPXHAwU8nmrHzg=; b=JjUstG2KsFsXANBTc/L263RH74G0dBfOa34TPOYP8cEtsyDgR9uGbgdLskHGq+ZGd4 HhNwEtsJ7fSe09Vfw7oYNx3xKct4X/LKX6eScIjSO+1cVJOPMSUsj2pRvZOkI6MAhNAf WzDw+rcN1B8y09sxJ2B2JC7loIFupMZJcYLCLET9M6YyWV58WnRQkqKLj0a1Mw8YAvL0 P1ujI4FFLY5TpvDJpvlIJxD/GqJPP5xbZzCMTs3IN+aCK9AwbfAXXUYrPGQVoXFusg+0 d64t7t0PXcDrKION0mOQn6x+UNR5z9EN1lxszzyA+bNlcf3AXWh68oIc3HxHVUzGWaMF PE1g== X-Received: by 10.224.65.6 with SMTP id g6mr1203138qai.4.1365253075089; Sat, 06 Apr 2013 05:57:55 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.49.1.4 with SMTP id 4ls1240865qei.68.gmail; Sat, 06 Apr 2013 05:57:53 -0700 (PDT) X-Received: by 10.49.116.165 with SMTP id jx5mr1260008qeb.22.1365253073072; Sat, 06 Apr 2013 05:57:53 -0700 (PDT) In-Reply-To: <1f964e4b-2762-43b8-85e5-41392926b07a@isocpp.org> X-Original-Sender: benjameslindley@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:3592 Archived-At: ------=_Part_25_3558348.1365253072562 Content-Type: text/plain; charset=ISO-8859-1 I think this is a great idea. Yes, it would be preferred to do what Sandoval mentioned, and return from a function, but why not have this option too? It seems to me that it is exactly as the OP said > "Easy to understand. Easy to implement. 100% backwards compatible." > I'm not sure how it makes the intention obscure. Two breaks in a row means break, then break again. 3 breaks means break, then break, then break. I would even suggest an addition. The ability to add one continue to a series of breaks. -- --- 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. ------=_Part_25_3558348.1365253072562 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I think this is a great idea.  Yes, it would be preferred to do w= hat Sandoval mentioned, and return from a function, but why not have this o= ption too?  It seems to me that it is exactly as the OP said
 
"Eas= y to understand. Easy to implement. 100% backwards compatible."

I'm not sure how it makes the intention obscure. Two breaks in a r= ow means break, then break again.  3 breaks means break, then break, t= hen break.  I would even suggest an addition.  The ability to add= one continue to a series of breaks.

--
 
---
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.
 
 
------=_Part_25_3558348.1365253072562-- .