220 17805 article Path: news.gmane.org!not-for-mail From: drax325 Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: warning usage operator Date: Tue, 12 May 2015 18:42:59 -0700 (PDT) Lines: 72 Approved: news@gmane.org Message-ID: Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_2255_1967393086.1431481379612" X-Trace: ger.gmane.org 1431481385 7139 80.91.229.3 (13 May 2015 01:43:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 13 May 2015 01:43:05 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBDD5TZHT5QPBBJGYZKVAKGQEIWZCULI@isocpp.org Wed May 13 03:43:02 2015 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-yh0-f69.google.com ([209.85.213.69]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YsLhN-0007WY-Nm for gclcip-std-proposals@m.gmane.org; Wed, 13 May 2015 03:43:01 +0200 Original-Received: by yhmu66 with SMTP id u66sf20870358yhm.2 for ; Tue, 12 May 2015 18:43:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:subject:mime-version:content-type :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe; bh=8O+7p+edgKDjOFcm8oJ29743gRUp73oUO5fSA+Z7UnE=; b=JAA+q9n33K0VNuhpfj8uWF2T/KbgUxfc64DclaT9hTy+p1zSjtIlQMTzGkrp4MShNa 4u56B/5MZ5pmH0Qv2koUDuwGMspsuD8Be8MXimDip56rcrtAuMcCUIbl1/UfOivepi4+ eIDxHtj0pNmGprigtgKFf0ZLi6dOmnJjypmAWalM9Qx2wLKS3ljCOMhvBK9tpYztfwGm KFeXwiXPJkHl88sRo+qbX1UczvkSy5sBfOhTCg0Qu8UNRmNub3wei1QFeZnx3EcHJqJf LTU2CftEguT9mvnAYj5Hy+RolVDg7ckCCNNHzbqFhaYMETdxl46oeICt+Fww/aH8mY2i XauA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:message-id:subject:mime-version :content-type:x-original-sender:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:list-subscribe :list-unsubscribe; bh=8O+7p+edgKDjOFcm8oJ29743gRUp73oUO5fSA+Z7UnE=; b=c4IAXO4uLQsFrAq8qqNERUEuDw/vNvQwVrRgU1mE61FhmjFFQpZSSiJBWgOC1fTeFC hVIB7Gc/0Y6UPPpy+hRvrayzTXkrVW4TJh0a3tuulZlEkI0P+5QKROgyhMZ6nvdCToHw Ld/16Gk4+HmD2mmw+ZfW8yWhq9+hYcGK+vHhioYL8P680rrDK8gI1cPe76xWR+CyN4+I 6xreiL2y9I5hTrrVGkefaOzeS7CYL0hQo4oJYxfXzRw8No+ysJzUGsVH8cYmofAN+VQj 3fB5t48V3g673tOEtWAD258Gx/sUii3iFUwiZrqVMF55GazqCL4olk5jyYLgmRJbz4hp SicQ== X-Gm-Message-State: ALoCoQlPfpY4iL9x1Tz+t68nNRqZ4TQIyO813c0kiWAMrHhChlr1zFrCSazi81b1cnUJi1qQD2qP X-Received: by 10.140.145.199 with SMTP id 190mr30284126qhr.2.1431481380723; Tue, 12 May 2015 18:43:00 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.182.165.3 with SMTP id yu3ls150492obb.8.gmail; Tue, 12 May 2015 18:42:59 -0700 (PDT) X-Received: by 10.182.236.39 with SMTP id ur7mr133713obc.23.1431481379934; Tue, 12 May 2015 18:42:59 -0700 (PDT) X-Original-Sender: draxlerm@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:17805 Archived-At: ------=_Part_2255_1967393086.1431481379612 Content-Type: multipart/alternative; boundary="----=_Part_2256_1169883543.1431481379612" ------=_Part_2256_1169883543.1431481379612 Content-Type: text/plain; charset=UTF-8 I'm not sure if this would solve any problems, but I was thinking it might be an alternative way of thinking about things. A lot of programming time is spent on error checking/preventing. A common tactic is to have if control statement to check before usage. Or using exception handling. what if there was an operator that you could overload, it doesn't have a syntax operator , but it would be called any time the object is used. If the operator is not defined the code would operate as it does today. Whether it used in a function or assigned to another variable. If a class does use throwing functions to warn about internal states, this single operator could be a way to combine it into one location, and it works for places outside of class definition. Any opinion, just throwing things out there. -- --- 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/. ------=_Part_2256_1169883543.1431481379612 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I'm not sure if this would solve any problems, but I was t= hinking it might be an alternative way of thinking about things.

A lot of programming time is spent on error checking/preventing.&n= bsp;
A common tactic is to have if control statement to check bef= ore usage. Or using exception handling. 

what= if there was an operator that you could overload, it doesn't have a syntax= operator , but it would be called any time the object is used. If the oper= ator is not defined the code would operate as it does today.

=
Whether it used in a function or assigned to another variable.

If a class does use throwing functions to warn abou= t internal states, this single operator could be a way to combine it into o= ne location, and it works for places outside of class definition.

Any opinion, just throwing things out there. 

--

---
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.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/<= /a>.
------=_Part_2256_1169883543.1431481379612-- ------=_Part_2255_1967393086.1431481379612-- .