220 14255 article Path: news.gmane.org!not-for-mail From: murman@gmail.com Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Comment on N4165, N4174 Date: Mon, 27 Oct 2014 10:45:41 -0700 (PDT) Lines: 77 Approved: news@gmane.org Message-ID: References: Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_3974_100266043.1414431942061" X-Trace: ger.gmane.org 1414431950 14383 80.91.229.3 (27 Oct 2014 17:45:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 27 Oct 2014 17:45:50 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBCHZJF6GWYLBBRUJXKRAKGQEQYG7LQA@isocpp.org Mon Oct 27 18:45:45 2014 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-pa0-f71.google.com ([209.85.220.71]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XioMS-00034M-UL for gclcip-std-proposals@m.gmane.org; Mon, 27 Oct 2014 18:45:45 +0100 Original-Received: by mail-pa0-f71.google.com with SMTP id rd3sf37928236pab.6 for ; Mon, 27 Oct 2014 10:45:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe :content-type; bh=L661UMg+RNH2XqnoWeuETd/zbKoxMt+PZKpDVYdnuRU=; b=p7zrkdnIqrrIaDefVwiB3FKs7dS2nEcxsYVSNm3QPBxd64TRldHOqPDdk+QcpqTai/ 2gR/nd4GgZhIA00ma6N2H/UDobIEjeW08urLWA6qqdN6wHRPfBn6qKJtxrPJxw7M7IY4 z8315qU/uq2C1Ghp+SXBZOD3rkh17vhZhuAipFsiRe3ELHyWnIOO+RoEwmP01Ab51MlK j78RLuE20QWX707/5m4ehozwZcLIpGcj5X4l9ZzcohjbpGrYZOHP9pUGOzeeAdQ2kX90 UfaiouoRPckp+zi0AKSEhIpEvteJh0WEzstkhRVbB5RqUND8k5AXAukLJKMLf3+GuwtU PWIA== 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:in-reply-to:references :subject:mime-version:x-original-sender:reply-to:precedence :mailing-list:list-id:list-post:list-help:list-archive :list-subscribe:list-unsubscribe:content-type; bh=L661UMg+RNH2XqnoWeuETd/zbKoxMt+PZKpDVYdnuRU=; b=fPTYKMpViepoQu0nCfDOijBvwQkGSjXPjXQsaE36c6Pqyvrzm4gzvFRzex+X4TfN1Y 80xnJdAvgXl2sqBbq4FSIyp8w0x+m0sObVz5kY6FP5wvTlJWl+2sOxAXYyDq94+ePdVY 1/arjg3GlnhyoTUTl5CvMOHk25FJXg9Ug9W0MqykCjGJckEce/dhTJpJG0kmRyeGuRKO 5596M0QX/mkKunuV5Krc2TEISmu7FUODMmKHY1oRgwf8PHM35TxydNV9ehrwe/wxtGpz v7hmTAgcRJscID7b2O+3yclDRKi3nLOe+P6437OGpoLd+TIFdPhBB+GEMcytsIj8XJgp LgeQ== X-Gm-Message-State: ALoCoQmJLYgJlQ2Bn3GUK4+FBoOUlylzZXOoxNBxgOtfvCSXsYM5ka0awYEdgG6NwLWgmpfLKKBI X-Received: by 10.66.102.68 with SMTP id fm4mr21865099pab.42.1414431943602; Mon, 27 Oct 2014 10:45:43 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.182.143.7 with SMTP id sa7ls913467obb.95.gmail; Mon, 27 Oct 2014 10:45:42 -0700 (PDT) X-Received: by 10.182.60.37 with SMTP id e5mr156291obr.2.1414431942749; Mon, 27 Oct 2014 10:45:42 -0700 (PDT) In-Reply-To: X-Original-Sender: murman@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:14255 Archived-At: ------=_Part_3974_100266043.1414431942061 Content-Type: text/plain; charset=UTF-8 On Monday, October 27, 2014 3:24:31 AM UTC-5, Ryou Ezoe wrote: > > I have some comments on N4165/N4174. > > 1. weird code > It's my understanding that under this proposal, following code is > well-formed. > > 4.0.sqrt() ; > "hello".puts() ; > I have similar concerns, largely around the number of applicable free functions for common types such as int, and whether literals or only named values will participate in unified call syntax. Assuming literals of plain types participate, it would be good to specifically address calling free functions on integers, as Python has some initially surprising parsing in this area: http://stackoverflow.com/questions/10955703/accessing-a-python-int-literals-methods -- Michael Urman -- --- 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_3974_100266043.1414431942061 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Monday, October 27, 2014 3:24:31 AM UTC-5, Ryou Ezoe wr= ote:
I have some comments on N4= 165/N4174.

1. weird code
It's my understanding that under this proposal, following code is well-= formed.

4.0.sqrt() ;
"hello".puts() ;

I have similar concerns, largely aroun= d the number of applicable free functions for common types such as int, and= whether literals or only named values will participate in unified call syn= tax. Assuming literals of plain types participate, it would be good to spec= ifically address calling free functions on integers, as Python has some ini= tially surprising parsing in this area:

http://sta= ckoverflow.com/questions/10955703/accessing-a-python-int-literals-methods

-- 
Michael Urman

--

---
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_3974_100266043.1414431942061-- .