220 27900 <616f8567-2214-4424-a1e3-85ce70e5c99b@isocpp.org> article Path: news.gmane.org!.POSTED!not-for-mail From: Nicol Bolas Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Re: Stabilize the numeric types in all platforms Date: Tue, 23 Aug 2016 06:33:08 -0700 (PDT) Lines: 136 Approved: news@gmane.org Message-ID: <616f8567-2214-4424-a1e3-85ce70e5c99b@isocpp.org> References: <72b7e733-cb85-4f47-a09b-10611f04211b@isocpp.org> <18a39611-8088-4e04-be0a-bb1b7c485683@isocpp.org> <1706311.trY4MaExHO@tjmaciei-mobl1> <36958399-1282-4cef-a12b-0439e176aeda@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_389_1793943491.1471959189020" X-Trace: blaine.gmane.org 1471959200 2027 195.159.176.226 (23 Aug 2016 13:33:20 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 23 Aug 2016 13:33:20 +0000 (UTC) To: ISO C++ Standard - Future Proposals Original-X-From: std-proposals+bncBCEKFTV6ZUMBBFVB6G6QKGQEC2GKIZQ@isocpp.org Tue Aug 23 15:33:15 2016 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-pa0-f70.google.com ([209.85.220.70]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bcBpG-0008Qs-LA for gclcip-std-proposals@m.gmane.org; Tue, 23 Aug 2016 15:33:10 +0200 Original-Received: by mail-pa0-f70.google.com with SMTP id le9sf261583473pab.0 for ; Tue, 23 Aug 2016 06:33:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isocpp-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=ZNxD21UF0dB8MBlnhjMAkG+NVHl3nt/pKB1y7ECiFwo=; b=x48PDvGxpks8vY5WMiFF65qANnd4AVjxYQRTs/BPvW+GY0Ty6/X5GsO8bIPW6nCyfk Lf6lOC0Tw1NcvyBtN5NNXMd2QEL20vlsxTN1zE1k8zgaGNCTZAZJ2U5EanVtdPiLjMHb bvUmsZYTdaZJdIRkCcPPVDpFD4exDP9Jd7lgdhXcZA1lVbyA6HSNGzbL8/pahYYQEa9c 9y7p19Q8AiFRVLhLhNAoj1H5BV0eqXtVPfKMntTX56h8OHcbwUJN8Ceu4eRhl6O1wJlq LRP+ettT3sz3RFbjtI3A6Ot4ZukVfuvrJtPJWTpN2+zYriex6c+O2OD/cwUmjfo6P+Iu WjyA== 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 :x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=ZNxD21UF0dB8MBlnhjMAkG+NVHl3nt/pKB1y7ECiFwo=; b=0YRMzLDL304PPNm4tCFewlxwBUXFs6zA6+ZySSh03quSvpEErYNo2TvtMx7/HD9sbK Fk8EDQjrAjJmG+wENTI+i08UCLt61c+l0ZKci7ObRrVM/g6RUhUKfzFTycIMMxp3Cj2c 7/gdYD4nAkvErHkCWYDZ7rb2nSxubvZlMH6FsYB3Dvr2GVHXg0BOdw+/neJtDpZJzN6R Yuurwat7QeHg1eeTI0VZGfb25XgqUyBYBlkAlt6c6LmqNw48uEwG5fXBdLqBrgIRiFHo JLoFywxayiUpHxZ1AHwSYnxAr6oMKqNQRNPXeGp+u+HflZ4ZZFpYIHd15DPgIF88glKJ UEZw== 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:x-spam-checked-in-group:list-post:list-help :list-archive:list-subscribe:list-unsubscribe; bh=ZNxD21UF0dB8MBlnhjMAkG+NVHl3nt/pKB1y7ECiFwo=; b=j/J7/eB7uf+V5Cgrkg2tln88VIJ71XZl3OpQ1ghOBG5C5GtxreudN4lvgvtT9irZiY //rnC/Dc7x17QO8hajpcQYUjeXTl4Gs7XGuCoPBsRrkR1+YrotpsHfx8WcNhH+r+ll+6 GE8LVm0ZUtw452a4+KJP3k6vg2Mq3auGElpyoGeRKehQqKvIJXl2E6B+bS0h1Kod2c+G YXua4TPlS5vR9iGX+RbdUokuu59HFO/SN5Ixi6a6KqYnYVZg8XYnbD6/16WQDJeSPWkx 0HQ1zc3PbAO9uPrClcTL8AqXsoT8jlTK5I7tJZ+WdISN55hiTOn/jKJhUd+Lv7ggshKy M7Yw== X-Gm-Message-State: AEkoousAGWlX4prQFlUyFEXukGFINatZjUZw1OrxcuOf+op8Q4EUTGezDUCoinMhGLbqwg== X-Received: by 10.67.7.233 with SMTP id df9mr20880398pad.4.1471959191059; Tue, 23 Aug 2016 06:33:11 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.36.238.5 with SMTP id b5ls4824131iti.3.gmail; Tue, 23 Aug 2016 06:33:10 -0700 (PDT) X-Received: by 10.36.111.147 with SMTP id x141mr848003itb.6.1471959190079; Tue, 23 Aug 2016 06:33:10 -0700 (PDT) In-Reply-To: <36958399-1282-4cef-a12b-0439e176aeda@isocpp.org> X-Original-Sender: jmckesson@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:27900 Archived-At: ------=_Part_389_1793943491.1471959189020 Content-Type: multipart/alternative; boundary="----=_Part_390_1598992881.1471959189020" ------=_Part_390_1598992881.1471959189020 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tuesday, August 23, 2016 at 7:31:20 AM UTC-4, FrankHB1989 wrote: > > =E5=9C=A8 2016=E5=B9=B48=E6=9C=8823=E6=97=A5=E6=98=9F=E6=9C=9F=E4=BA=8C U= TC+8=E4=B8=8B=E5=8D=8812:49:54=EF=BC=8CThiago Macieira=E5=86=99=E9=81=93=EF= =BC=9A >> >> On segunda-feira, 22 de agosto de 2016 21:36:12 PDT FrankHB1989 wrote:= =20 >> > OK, I should have said, they are not mandated *by the core language*,= =20 >> or,=20 >> > not guaranteed both built-in and portable.=20 >> >> They are mandated in a header that complements the core language. Just= =20 >> like=20 >> , and , those types cannot be=20 >> implemented by anyone except the compiler vendor.=20 >> >> Therefore, for all intents and purposes, the minimum-width and fast=20 >> integer=20 >> types are guaranteed to be portable.=20 >> >> The exact-width ones aren't guaranteed to be portable because their=20 >> concept=20 >> isn't portable. Some machines don't have 8-, 16-, 32- and 64-bit types= =20 >> (they=20 >> could be multiples of 9 bits). Also note how int32_t is required to use= =20 >> two's=20 >> complement representation, which again excludes some machines.=20 >> >> Good point about 2's complements. However, all of these are what I have= =20 > already known. I still wonder why these (at least partially) width-aware= =20 > types are not in the core language while traditional fundamental integer= =20 > types are still in it. > .... why does it matter if it's a reserved keyword or not? It's *there*;=20 it's available on every platform that provides C++11 or better. You can use= =20 it to solve the problem you have with types not having a relatively fixed= =20 size. The placement of something in the standard library or core language is not= =20 based on some evaluation of the *merit* of the feature. --=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. To view this discussion on the web visit https://groups.google.com/a/isocpp= ..org/d/msgid/std-proposals/616f8567-2214-4424-a1e3-85ce70e5c99b%40isocpp.or= g. ------=_Part_390_1598992881.1471959189020 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Tuesday, August 23, 2016 at 7:31:20 AM UTC-4, FrankHB19= 89 wrote:
=E5= =9C=A8 2016=E5=B9=B48=E6=9C=8823=E6=97=A5=E6=98=9F=E6=9C=9F=E4=BA=8C UTC+8= =E4=B8=8B=E5=8D=8812:49:54=EF=BC=8CThiago Macieira=E5=86=99=E9=81=93=EF=BC= =9A
On segunda-feira, 22 de agosto d= e 2016 21:36:12 PDT FrankHB1989 wrote:
> OK, I should have said, they are not mandated *by the core languag= e*, or,=20
> not guaranteed both built-in and portable.

They are mandated in a header that complements the core language. Just = like=20
<intializer_list>, <type_traits> and <limits>, those = types cannot be=20
implemented by anyone except the compiler vendor.

Therefore, for all intents and purposes, the minimum-width and fast int= eger=20
types are guaranteed to be portable.

The exact-width ones aren't guaranteed to be portable because their= concept=20
isn't portable. Some machines don't have 8-, 16-, 32- and 64-bi= t types (they=20
could be multiples of 9 bits). Also note how int32_t is required to use= two's=20
complement representation, which again excludes some machines.

Good point about 2's complements. However, all of= these are what I have already known. I still wonder why these (at least pa= rtially) width-aware types are not in the core language while traditional f= undamental integer types are still in it.

= .... why does it matter if it's a reserved keyword or not? It's t= here; it's available on every platform that provides C++11 or bette= r. You can use it to solve the problem you have with types not having a rel= atively fixed size.

The placement of something in the standard libra= ry or core language is not based on some evaluation of the merit of = the feature.

--
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.
To view this discussion on the web visit https://groups.google.= com/a/isocpp.org/d/msgid/std-proposals/616f8567-2214-4424-a1e3-85ce70e5c99b= %40isocpp.org.
------=_Part_390_1598992881.1471959189020-- ------=_Part_389_1793943491.1471959189020-- .