220 5516 article Path: news.gmane.org!not-for-mail From: Steve Heller Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Re: A library to provide a virtual memory vector of strings Date: Tue, 23 Jul 2013 09:34:35 -0500 Lines: 134 Approved: news@gmane.org Message-ID: References: <861959e9-74f3-4ed8-aeca-bad9c3256acd@isocpp.org> <2896e1b4-1e3c-493e-b61b-7c1ae955de46@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e0116026a2b3ad704e22eb15e X-Trace: ger.gmane.org 1374590080 12694 80.91.229.3 (23 Jul 2013 14:34:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 23 Jul 2013 14:34:40 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBDG2H26ZRUARB65IXKHQKGQEIXWJ57Q@isocpp.org Tue Jul 23 16:34:43 2013 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-ob0-f198.google.com ([209.85.214.198]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1V1dfh-0002qi-E9 for gclcip-std-proposals@m.gmane.org; Tue, 23 Jul 2013 16:34:37 +0200 Original-Received: by mail-ob0-f198.google.com with SMTP id up14sf33243677obb.5 for ; Tue, 23 Jul 2013 07:34:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-beenthere:mime-version:in-reply-to:references:date:message-id :subject:from:to:x-original-sender:x-original-authentication-results :reply-to:precedence:mailing-list:list-id:x-google-group-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe :content-type; bh=GHIze5oPA8eWwaYKUhR6B05wk7kwl0+vZlVwzxSjM94=; b=U+WyMXN9NEFcGB1125EP4oNwxvhECvxs0HGLtRpB2EqJ+GqfgvVDXgf2xCnONCgylF Md3GPYpZYqDn32o/vQp09UvLGHONXizz1xyoujI1VgE/kk95k/mQgv4zs1o00RMYd3UX 7SwezfGSc1vEroBWT35FhD6zyy8A6dXJMcoV7lOgB6TL7beAvgIn4K7K/3ezUW/U1Oc+ dvTvK/cGezg0lv4GWuqcsF4J3LRLJD9bCBebgd8moz684hsGe4kr725f4LGN/Y/mBzzE peqxdLZzYXWYN9L7vlZvPx1UxiPXRH8FVn0pqmguZN+bd5O52j6XfYsGv1dJ9uVhpFHR JMYw== X-Received: by 10.182.71.44 with SMTP id r12mr8456172obu.25.1374590076308; Tue, 23 Jul 2013 07:34:36 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.182.118.137 with SMTP id km9ls1295232obb.7.gmail; Tue, 23 Jul 2013 07:34:35 -0700 (PDT) X-Received: by 10.60.97.200 with SMTP id ec8mr30742900oeb.33.1374590075798; Tue, 23 Jul 2013 07:34:35 -0700 (PDT) Original-Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [2607:f8b0:4003:c01::22c]) by mx.google.com with ESMTPS id u6si18586402oes.133.2013.07.23.07.34.35 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 23 Jul 2013 07:34:35 -0700 (PDT) Received-SPF: pass (google.com: domain of technovelist@gmail.com designates 2607:f8b0:4003:c01::22c as permitted sender) client-ip=2607:f8b0:4003:c01::22c; Original-Received: by mail-ob0-f172.google.com with SMTP id wo10so10191556obc.17 for ; Tue, 23 Jul 2013 07:34:35 -0700 (PDT) X-Received: by 10.60.94.136 with SMTP id dc8mr30725913oeb.89.1374590075613; Tue, 23 Jul 2013 07:34:35 -0700 (PDT) Original-Received: by 10.60.28.100 with HTTP; Tue, 23 Jul 2013 07:34:35 -0700 (PDT) In-Reply-To: X-Original-Sender: technovelist@gmail.com X-Original-Authentication-Results: mx.google.com; spf=pass (google.com: domain of technovelist@gmail.com designates 2607:f8b0:4003:c01::22c as permitted sender) smtp.mail=technovelist@gmail.com; dkim=pass header.i=@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:5516 Archived-At: --089e0116026a2b3ad704e22eb15e Content-Type: text/plain; charset=ISO-8859-1 Well, since this library and its predecessor implementations have been around for at least 30 years, I'm pretty sure that the underlying ideas are sound. As for the current implementation, it is in use in my current employer's products and has been very helpful in reducing memory consumption without causing any significant problems. On Tue, Jul 23, 2013 at 9:23 AM, Ville Voutilainen < ville.voutilainen@gmail.com> wrote: > > > > On 23 July 2013 17:16, Steve Heller wrote: > >> An earlier implementation has been published, in my optimization books, >> including "Optimizing C++". I have made significant improvements to it >> since then, however, including read-only access and a number of speed >> optimizations and capacity improvements. >> >> I don't see the utility of trying to get it into Boost, so long as the >> committee is interested in it. >> >> > The reason going via boost is recommended is gaining implementation and > user experience, and thus > fix problems before standardization. Chances are that it's faster to get > something out there via boost. > That would be its utility, but as I said, it's not a prerequisite, for > various reasons people occasionally > choose not to go via boost. > > -- > > --- > 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/. > > > -- --- 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/. --089e0116026a2b3ad704e22eb15e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Well, since this library and its predecessor implementations have been arou= nd for at least 30 years, I'm pretty sure that the underlying ideas are= sound. As for the current implementation, it is in use in my current emplo= yer's products and has been very helpful in reducing memory consumption= without causing any significant problems.

On Tue, Jul 23, 2013 at 9:23 AM, Ville Vouti= lainen <ville.voutilainen@gmail.com> wrote:



On 23 July 2013 17:16, Steve Heller <techno= velist@gmail.com> wrote:
An earlier implementation has been published= , in my optimization books, including "Optimizing C++". I have ma= de significant improvements to it since then, however, including read-only = access and a number of speed optimizations and capacity improvements.

I don't see the utility of trying to get it into Boost, = so long as the committee is interested in it.


The reason going via boost is recommended is gaining= implementation and user experience, and thus
fix problems before standardization. Chances are that it's faster to ge= t something out there via boost.
That would be its utility, b= ut as I said, it's not a prerequisite, for various reasons people occas= ionally
choose not to go via boost.

--
=A0
---
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/gro= up/std-proposals/.
=A0
=A0

--
 
---
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>.
 
 
--089e0116026a2b3ad704e22eb15e-- .