Re: [boost] [RFC] string inserter/extractor "q u o t i n g"

Subject: Re: [boost] [RFC] string inserter/extractor "q u o t i n g"
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-06-18 06:38:38

Beman Dawes wrote:
>
> To speed the process, I'll just give a progress report rather than
> respond individually prior messages.

Apparently, by virtue of not mentioning my suggestion in this omnibus reply, you rejected my idea of a string algorithm for doing the quoting and unquoting which forms the foundation of the insertion and extraction manipulators.  I still think that is the best approach as it doesn't force the use of std::stringstream to get a quoted or unquoted string from an existing string while still supporting the IOStream insertion and extraction needed by Filesystem.

> * I like quote and unquote as the names. Source changed.

Given the name change, my suggestion is for "quoted" as the manipulator -- for both insertion and extraction -- and "quote" and "unquote" for the algorithms.

> * Since these functions are I/O manipulators, and only work in that
> context, I've renamed the header "quote_manip.hpp".
>
> * Likewise, the library that makes the most sense to add the header
> too is io. So the include path will be <boost/io/quote_manip.hpp>. IO
> is a small library, and targets exactly the same area of the standard
> library.

That's reasonable for the manipulators, but the algorithms on which they'd be based, given my suggestion, should be in StringAlgos.

> See
> <https://svn.boost.org/svn/boost/branches/filesystem3/boost/io/quote_manip.hpp>

I get a 404 error trying to access that file.

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer, Core Software      using std::disclaimer;
Susquehanna International Group, LLP  http://www.sig.com

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.