Re: [boost] Formal Review Request: Boost.String.Convert

Subject: Re: [boost] Formal Review Request: Boost.String.Convert
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2009-02-17 14:55:15

On Tuesday, February 17, 2009 2:51 PM
Emil Dotchevski wrote:
> On Tue, Feb 17, 2009 at 11:43 AM, Stewart, Robert
> <Robert.Stewart_at_[hidden]> wrote:
> > On Tuesday, February 17, 2009 2:39 PM
> > Emil Dotchevski wrote:
> >>
> >> My question is, what is the motivation for the convert function?
> >> What's the use case for it that doesn't work with
> >> to_string/from_string?
> >
> > That was my suggestion to account for both conversion
> directions and eliminate "string" from the name, thus opening
> the interface to other conversions.
>
> An interface that converts anything to anything else is a separate
> issue, and requires a separate discussion.
>
> If we concentrate on converting from and to string, I think that two
> families of functions, to_string and from_string is the most logical
> approach. When I want a string, I know that I want a string and at
> that time I don't care about any other conversions. I can't think of a
> use case when I might want a string but might also want something
> else.

The arguments, whether function or template, would specify the conversion to apply.  For example, to_string<int>(s) could also be written as convert<int>(s).  (Both can be rearranged to take two arguments and return a bool, for example, so the point is merely to eliminate directionality and "string" from the name.)

_____
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.