220 11973 article Path: news.gmane.org!not-for-mail From: =?UTF-8?Q?R=C3=B3bert_D=C3=A1vid?= Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: User defined literal for size_t Date: Sun, 20 Jul 2014 03:43:46 -0700 (PDT) Lines: 74 Approved: news@gmane.org Message-ID: References: <92f06dea-7599-4641-8448-f2c0904d520a@isocpp.org> <4A1CB989-25B3-4D30-8A5E-31EBBC39733D@gmail.com> <769ba8b7-e320-4a50-8a17-6d01a2d43a05@isocpp.org> <5A048F7E-F3DE-4111-A4A0-E28D84A3A56D@gmail.com> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1448_1477657767.1405853026438" X-Trace: ger.gmane.org 1405853040 29226 80.91.229.3 (20 Jul 2014 10:44:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 20 Jul 2014 10:44:00 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBDMKHJ4B6MARBY52V2PAKGQE4VRBSPA@isocpp.org Sun Jul 20 12:43:49 2014 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-vc0-f199.google.com ([209.85.220.199]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1X8oaq-00018u-Se for gclcip-std-proposals@m.gmane.org; Sun, 20 Jul 2014 12:43:49 +0200 Original-Received: by mail-vc0-f199.google.com with SMTP id la4sf16430848vcb.2 for ; Sun, 20 Jul 2014 03:43:48 -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=Ix/SHh3OibIqZWOhOSLU6YqDLUgkmOUsPmZMEBmd4vs=; b=IbMNsYAERO98iXDmQ9vU4+CUPeFMdBkJz2Otp4yT4SUo7dwH88VnnL81MHZqMBWwur LUqN7Qb8Pft8N9L7W7cC79KP5zvPgrh2M6ko+VWBatWa4EG5T4gxFrdHrXNQgw3mzFxK IMI2tpTTSGVkko15Nhn1+D9THR+8adWGfGvmiFxLr/XDX3c7R3FcBa7FU69ENW22OjOk hqHfMEFcHvVx3v0tJZpLTDWDk+pXAmjXC1J+g2ZXtOmNz4NPPUXUaVpJ8ou1bC6f/5ig DCfirslsF9F+qP01UKrWUfkMS98L4QR80SnklnPsfgaoNwTYmHLc+paroFenj3he5hrk wZFg== 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=Ix/SHh3OibIqZWOhOSLU6YqDLUgkmOUsPmZMEBmd4vs=; b=eTthqXZeMnwCE3/wrNBkb2sYbDXg+9N12r7mDzbd+1yFSsz7CNB8io73ZSrmUcrQv6 zMgi04PTv+wDdg7AbDKoExUdbZLjOHlqUILXqPRwX6NJ2qmGotAluRawjF+3lUpZVy9Q Kz4Li5qHVzy+x2t0cAwbeeZEBUwHZY3IYLXT92HkJnrOJn0+xgMQg6RdHWfGj6R767A4 OmkxN0BL8M/FzkhyLoYMi7OizZIHha37djF46M0k8wDRZMBpxae6wPueB9XxHPy8Lb1v ADkjm2rv2RTfUUW3kmahp8BnY3O/7pTAMq4OO9kdw3DhlDGJ428lu8YMA0TWtxJ+XZFA LWkg== X-Gm-Message-State: ALoCoQlagQ3MMGu3UuHZj3zpR5JubQHyxlV++hXIMJO5WT24fgLe6H6gu281cr4hRIfqBuYd87eS X-Received: by 10.236.4.132 with SMTP id 4mr7641455yhj.28.1405853027981; Sun, 20 Jul 2014 03:43:47 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.140.95.193 with SMTP id i59ls1562698qge.20.gmail; Sun, 20 Jul 2014 03:43:47 -0700 (PDT) X-Received: by 10.140.21.175 with SMTP id 44mr804qgl.14.1405853027307; Sun, 20 Jul 2014 03:43:47 -0700 (PDT) In-Reply-To: <5A048F7E-F3DE-4111-A4A0-E28D84A3A56D@gmail.com> X-Original-Sender: lrdxgm@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:11973 Archived-At: ------=_Part_1448_1477657767.1405853026438 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 2014. j=C3=BAlius 20., vas=C3=A1rnap 3:48:54 UTC+2 id=C5=91pontban David Kr= auss a=20 k=C3=B6vetkez=C5=91t =C3=ADrta: > > What second option? Can you elaborate what=E2=80=99s wrong with this line= of code? > =20 The one with a(n uint64_t) literal. There is nothing wrong with it, it's=20 just nothing better than the one using casting to unsigned long long, but= =20 there the programmer has given a less verbose choice to write a literal,=20 making unsigned long long a.. "more equal" citizen than uint64_t. As a totally unlikely alternative, if it *is* actually an intention to use= =20 (unsigned long long)1 instead of 1ull, why not remove/deprecate the literal= =20 suffixes? Robert --=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_1448_1477657767.1405853026438 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

2014. j=C3=BAlius 20., vas=C3=A1rnap 3:48:54 UTC+2 id= =C5=91pontban David Krauss a k=C3=B6vetkez=C5=91t =C3=ADrta:
What second option? Can you elaborate what=E2=80=99s wrong with this line = of code?
 
The one with a= (n uint64_t) literal. There is nothing wrong with it, it's just nothing bet= ter than the one using casting to unsigned long long, but there the program= mer has given a less verbose choice to write a literal, making unsigned lon= g long a.. "more equal" citizen than uint64_t.

As a totally unlikely= alternative, if it is actually an intention to use (unsigned long l= ong)1 instead of 1ull, why not remove/deprecate the literal suffixes?

Robert

--

---
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_1448_1477657767.1405853026438-- .