220 5518 article Path: news.gmane.org!not-for-mail From: Nicol Bolas 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 11:59:36 -0700 (PDT) Lines: 83 Approved: news@gmane.org Message-ID: References: <861959e9-74f3-4ed8-aeca-bad9c3256acd@isocpp.org> <52729d06-72f4-4d9d-a000-7cfa3af9837a@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_772_2238384.1374605976386" X-Trace: ger.gmane.org 1374605977 14076 80.91.229.3 (23 Jul 2013 18:59:37 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 23 Jul 2013 18:59:37 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBCEKFTV6ZUMBBGNFXOHQKGQEC3THLYY@isocpp.org Tue Jul 23 20:59:39 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 1V1hoB-0006Je-4a for gclcip-std-proposals@m.gmane.org; Tue, 23 Jul 2013 20:59:39 +0200 Original-Received: by mail-ob0-f198.google.com with SMTP id up14sf34718109obb.5 for ; Tue, 23 Jul 2013 11:59:38 -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=nPI4hl8gl78Dre6Nz/SBO61clbR5qZs95t+jijMVyZY=; b=0pzHKBVUPCLJ2zXT4zPCJWSOIBz+8EshNvfiaTTdbmI8weePNzJHYPcrL1eVdRDsGF cOpexP8Xp8vlEBn3A1za1GKmjM/gBnJsrM1eDjIZTVI3Y2a1fI9ywgBtLBqyREgId1QS lGznlWseuvpnW4ZHK/52LsnpEXBOHiQaGQQYIxX+RnotAqd3RIry+QEVB6l89SIDThkj YRyqVVlnbLwrM+Z9pQ4LIOhESsO3NHuZnvyX0bQkAD2uLF/4hDDi1GV5iCBhXMNKBPuh w1Y0fGpMxHN+iVcnw5sgw8rVxn2V956YE3tUZNVfR4Ajs2tuiziQn16UkvbwOpIwEthP YlZQ== X-Received: by 10.42.191.145 with SMTP id dm17mr22967189icb.11.1374605978039; Tue, 23 Jul 2013 11:59:38 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.50.1.7 with SMTP id 7ls1217085igi.0.gmail; Tue, 23 Jul 2013 11:59:37 -0700 (PDT) X-Received: by 10.50.30.226 with SMTP id v2mr10221igh.17.1374605977380; Tue, 23 Jul 2013 11:59:37 -0700 (PDT) In-Reply-To: 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:5518 Archived-At: ------=_Part_772_2238384.1374605976386 Content-Type: text/plain; charset=ISO-8859-1 On Tuesday, July 23, 2013 7:45:28 AM UTC-7, Steve Heller wrote: > > I admit that it *sounds* very special-case. But in practice it is a lot > more flexible than that. For example, my employer's programs use it in two > quite different applications, neither of which is a general string type. > Instead, it is used as the underlying storage mechanism for caching SQL > database records and for a domain-specific record type that is converted to > and from string representation (in this case, by the MFC CArchive facility). > > So rather than thinking of this as a virtual memory character string > facility, think of it as a mechanism for implementing file-based > variable-length data objects, and its more general applicability becomes > evident. > If that's what it's for, then you should probably describe and propose it that way. Another thing I'm leery about is that you seem to be describing the implementation, rather than the behavior. The standard is generally built around describing behavior, thus allowing implementers the freedom to implement it as they see fit. Tying this memory to files, for example, seems to be an implementation detail. Is there a more general way of describing it without dealing with implementation details? -- --- 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_772_2238384.1374605976386 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Tuesday, July 23, 2013 7:45:28 AM UTC-7, Steve Heller wrote:
I admit that it sounds very special= -case. But in practice it is a lot more flexible than that. For example, my= employer's programs use it in two quite different applications, neither of= which is a general string type. Instead, it is used as the underlying stor= age mechanism for caching SQL database records and for a domain-specific re= cord type that is converted to and from string representation (in this case= , by the MFC CArchive facility).

So rather than thinking of this as a virtual memory characte= r string facility, think of it as a mechanism for implementing file-based v= ariable-length data objects, and its more general applicability becomes evi= dent.

If that's what it's for, then you should p= robably describe and propose it that way.

Another thing I'm leery ab= out is that you seem to be describing the implementation, rather than the b= ehavior. The standard is generally built around describing behavior, thus a= llowing implementers the freedom to implement it as they see fit.

Ty= ing this memory to files, for example, seems to be an implementation detail= .. Is there a more general way of describing it without dealing with impleme= ntation details?

--
 
---
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_772_2238384.1374605976386-- .