220 5333 <708b8756-972d-46ce-8e66-2be484e9c4cd@isocpp.org> article Path: news.gmane.org!not-for-mail From: jalobado@gmail.com Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Allowing any integral type as an argument for user defined literal operators Date: Mon, 8 Jul 2013 04:35:38 -0700 (PDT) Lines: 80 Approved: news@gmane.org Message-ID: <708b8756-972d-46ce-8e66-2be484e9c4cd@isocpp.org> References: <80016e3a-2dc8-4887-b59b-a8aff20439e0@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_258_11292810.1373283338910" X-Trace: ger.gmane.org 1373303404 7577 80.91.229.3 (8 Jul 2013 17:10:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 8 Jul 2013 17:10:04 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBDSKP4PH2UKBBZXE5OHAKGQEUSXYMTY@isocpp.org Mon Jul 08 19:10:06 2013 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-yh0-f72.google.com ([209.85.213.72]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UwEwr-0008AU-30 for gclcip-std-proposals@m.gmane.org; Mon, 08 Jul 2013 19:10:01 +0200 Original-Received: by mail-yh0-f72.google.com with SMTP id z20sf6048840yhz.3 for ; Mon, 08 Jul 2013 10:10:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-beenthere:date:from:to: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=hrLZn228NtJuIJKiBw/9trX3H2vTPAxVak+VpRrbyNQ=; b=N668Kg6BsGs0XGAaFYaONTAzZ+OaJxZfjllRGbieeI8zd+Nu+DDV4f80UFk+ZZQUAc iVCc1VD2mZ3lMZzIsIaZV89ctpL9wpzjTHBVzoJrAlFE2DhPw+ybuReY+9n5qlT9L+1O FmDrsuHTH2UZFImYiyeFuQJxKUHn43dOVrSkYziIS2j7/RIVHRhyrEv/s8msFrVBtIVV CNi+fGr0CJuK3PPrWbwfCGrANihRjOBrU6TNFCH2gFZObu6gNwrO1osqWyGJN6tmSlBy y54rG6ua3hiFSe9Os3itWwgR1yu9Jk8qnZl3fii/Lj4EckSBI5nD3St3FFvAUQziFV1z rQDQ== X-Received: by 10.236.123.173 with SMTP id v33mr12166724yhh.31.1373303400145; Mon, 08 Jul 2013 10:10:00 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.49.106.134 with SMTP id gu6ls1940184qeb.83.gmail; Mon, 08 Jul 2013 10:09:58 -0700 (PDT) X-Received: by 10.224.129.196 with SMTP id p4mr25561304qas.6.1373303398653; Mon, 08 Jul 2013 10:09:58 -0700 (PDT) Original-Received: by 10.224.52.77 with SMTP id h13msqag; Mon, 8 Jul 2013 04:35:39 -0700 (PDT) X-Received: by 10.49.16.163 with SMTP id h3mr524289qed.24.1373283339223; Mon, 08 Jul 2013 04:35:39 -0700 (PDT) In-Reply-To: <80016e3a-2dc8-4887-b59b-a8aff20439e0@isocpp.org> X-Original-Sender: jalobado@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:5333 Archived-At: ------=_Part_258_11292810.1373283338910 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Saturday, July 6, 2013 10:26:19 PM UTC+2, Micha=C5=82 Dominiak wrote: > > Today I came across a very silly issue: you cannot do `uint64_t=20 > operator""_foo(uint64_t)`, because `uint64_t` is a typedef for `unsigned= =20 > long`, not `unsigned long long` on both Clang and GCC on Linux (despite t= he=20 > fact that `sizeof(unsigned long) =3D=3D sizeof(unsigned long long)`). You= have=20 > to type the long type name, just because the typedef isn't for the exact= =20 > type required by the standard. I hope we all agree this is a silly=20 > situation. I wasn't aware the standard required uint64_t to be typedef'ed to unsigned= =20 long long int. I wasn't even aware the standard required long long to be=20 64-bit in the first place. Last time I checked long long had to be at least= =20 64-bit but could be anything bigger. E.g. 128-bit would be OK. Can you=20 quote the chapter where the standard required uint64_t to be a typedef to= =20 unsigned long long? --=20 ---=20 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 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-proposa= ls/. ------=_Part_258_11292810.1373283338910 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Saturday, July 6, 2013 10:26:19 PM UTC+2, Micha=C5=82 Dominiak wrote:Today I came across a very silly = issue: you cannot do `uint64_t operator""_foo(uint64_t)`, because `uint64_t= ` is a typedef for `unsigned long`, not `unsigned long long` on both Clang = and GCC on Linux (despite the fact that `sizeof(unsigned long) =3D=3D sizeo= f(unsigned long long)`). You have to type the long type name, just because = the typedef isn't for the exact type required by the standard. I hope we al= l agree this is a silly situation.

I wasn't= aware the standard required uint64_t to be typedef'ed to unsigned long lon= g int. I wasn't even aware the standard required long long to be 64-bit in = the first place. Last time I checked long long had to be at least 64-bit bu= t could be anything bigger. E.g. 128-bit would be OK. Can you quote the cha= pter where the standard required uint64_t to be a typedef to unsigned long = long?

--
 
---
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-proposals/<= /a>.
 
 
------=_Part_258_11292810.1373283338910-- .