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 15:35:58

On Tuesday, February 17, 2009 3:25 PM
David Abrahams wrote:
> on Tue Feb 17 2009, Emil Dotchevski
> <emildotchevski-AT-gmail.com> wrote:
>
> > For example, to_string<int>(s) could also be written as
> > convert<int>(s).
>
> Probably just a slip of the mind, but:
>
>   to_string doesn't need a template parameter.  Explicitly
>   writing to_string<int>(s) is probably a bad idea and
> convert<int> would
>   correspond to from_string<int>(s).
>
> However, maybe we ought to ask why this keeps happening.  I think
> there's something about the convert<...>(...) interface that confuses
> people.  Eliminating directionality might not be such a hot idea.

There have been too many names and variations of signature for anyone to keep anything straight at this point.  convert() doesn't require specifying a template parameter.  The source and destination types can be deduced from the arguments, though that means the selected parameter order will confuse one group or another.

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