220 13555 article Path: news.gmane.org!not-for-mail From: Matthew Fioravante Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Re: Proposal: Strongly Typed Bitset Date: Thu, 2 Oct 2014 09:12:11 -0700 (PDT) Lines: 68 Approved: news@gmane.org Message-ID: References: <113390b2-9c74-47e2-a943-5d27dd48bdf1@isocpp.org> <41983d24-efb2-4255-b09b-f84cff7bf56d@isocpp.org> <76a65477-dc4e-4c77-92bd-8123e9ce7c0f@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_799_1118273478.1412266331369" X-Trace: ger.gmane.org 1412266341 26602 80.91.229.3 (2 Oct 2014 16:12:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 2 Oct 2014 16:12:21 +0000 (UTC) Cc: ricky.65@hotmail.com To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBDELF54RTIGRBW7SWWQQKGQEONN534I@isocpp.org Thu Oct 02 18:12:14 2014 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-ig0-f199.google.com ([209.85.213.199]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XZizF-0006wI-Ej for gclcip-std-proposals@m.gmane.org; Thu, 02 Oct 2014 18:12:13 +0200 Original-Received: by mail-ig0-f199.google.com with SMTP id hn18sf11555837igb.2 for ; Thu, 02 Oct 2014 09:12:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc: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=B/jx1hoKB2cfgOjEhn7NS1I1Di3Y6z7wl8/R5Tam/k0=; b=uyQfTDydqNL8JN0UfzYNjTexHSJed3AsLeSCf3SjOccsl4t84dFsc+DQCgrDAddApd gaC/1zuHxauEzQX7dgp/2H+pegrmoBRleucO80KxNKXxVO5ICZbp9DPRKQhD7DFuEiGY mkV2A25g0pp+PAqxRisuYOcsvkYQZpmCgGLf/omuCFMnpdXqy49y3B/zXmNI9+CATL5h WI9ezOzNGXd/sAO9DamshsS2VQ9/pzvBt2tQ+nF7UCkXfAJOdFw99yUK/KFvkY76Mejc WuZBXLZBNzOtDiAqjyuSIJIiojrpMPDMNMLUYT2LO/n+Co6LDF+Z8TYgH9K0Ylyo7ZEq 2QbQ== 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:cc: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=B/jx1hoKB2cfgOjEhn7NS1I1Di3Y6z7wl8/R5Tam/k0=; b=lPl33sn1gc+2U44iUeH/S7uJ6JtQXxvVQPedl4ubg6iQHM3YDdqSrHuD2Q6WTPqjGh adD3QedJWY3QwtieDIkgkVTI97ALjbBli6CJ0HrGvah3QVN6BBYz2fRc++K1tM3ALYB5 dXCZuVMu71aSN/QCh0tQKIBUYj2VCYMZBhyNvS8ewAH9OW2r005zdJGjBWm/ae9aLnM+ NJ1H/thTKMuQlZNQLmNR/XzL5Lx7zfHCw30TMVQ1B+WurSrJxhpjJAjrcT3p5RL7ExFx xHof8+b1DZAs35XVRfXAefM7kC82M6fsLnEHLzivo51WHZ3a8hsUPttPhfkeurSibnEL cB1Q== X-Gm-Message-State: ALoCoQnyn496oSvMCm2nXl2fdXZ8K1knOQYj7IJ4z3QIl0jt51WBXdo4PO7TL3HRVN4zWp9LG5dl X-Received: by 10.50.112.68 with SMTP id io4mr825721igb.0.1412266332555; Thu, 02 Oct 2014 09:12:12 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.140.51.103 with SMTP id t94ls903628qga.33.gmail; Thu, 02 Oct 2014 09:12:11 -0700 (PDT) X-Received: by 10.140.18.161 with SMTP id 30mr6975qgf.31.1412266331884; Thu, 02 Oct 2014 09:12:11 -0700 (PDT) In-Reply-To: <76a65477-dc4e-4c77-92bd-8123e9ce7c0f@isocpp.org> X-Original-Sender: fmatthew5876@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:13555 Archived-At: ------=_Part_799_1118273478.1412266331369 Content-Type: text/plain; charset=UTF-8 On Thursday, October 2, 2014 12:04:21 PM UTC-4, rick...@hotmail.com wrote: > > > Instead of that, to_string() could return std::array, which >> holds a null terminated bitstring. > > > I like the idea of returning a std::array but I'm not sure if a null > terminator is necessary. May I suggest the name "to_array" instead of > modifying to_string(). > > Better would be fixed_string (other thread) or string_literal (a real proposal). Anyway the string thing is just a minor rant. That's unrelated to this proposal. If raised in earnest I would write a new paper for that issue alone. -- --- 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_799_1118273478.1412266331369 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Thursday, October 2, 2014 12:04:21 PM UTC-4, ri= ck...@hotmail.com wrote:

Instead of that, to_string() could return s= td::array<char,N+1>, which holds a null terminated bitstring.

I like the idea of returning a std::array but I'm = not sure if a null terminator is necessary. May I suggest the name "to_arra= y" instead of modifying to_string().


Better would be fixed_string (other thread) or string_literal (a = real proposal). Anyway the string thing is just a minor rant. That's unrela= ted to this proposal. If raised in earnest I would write a new paper for th= at issue alone.
 

--

---
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_799_1118273478.1412266331369-- .