Re: [boost] [netlib] 0.8-beta now available!

Subject: Re: [boost] [netlib] 0.8-beta now available!
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-11-16 09:07:31

Dean Michael Berris wrote:
> On Tue, Nov 16, 2010 at 1:49 PM, Dean Michael Berris
> <mikhailberis_at_[hidden]> wrote:
> > On Tue, Nov 16, 2010 at 3:27 AM, Cliff Green
> <cliffg_at_[hidden]> wrote:
> >>
> >> Obviously, all of the internal / implementation code will
> >> use io_service_.
> >
> > Interesting. I was thinking that a unique_ptr would be more
> > appropriate, but as it currently stands using auto_ptr might make
> > sense in this case. It's worth a shot, thanks for the tip Cliff!
>
> And because it's so interesting, I just committed a set of changes to
> implement this. It's now on the cpp-netlib master and is going to be
> part of the 0.8 release on Friday.

I don't know whether you chose auto_ptr or unique_ptr, but in this case you should choose based upon which is less likely to increase application size since both otherwise suffice.  Using unique_ptr for io_service will increase code size unless the client already does the same, but as that is more likely than their using auto_ptr for io_service, at least in the future, using unique_ptr is probably wiser.  (If any standard library implementation were to use a void * implementation to share non-dependent code in unique_ptr, the code size could still be reduced if the client uses unique_ptr but not for io_service.)

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