Re: [boost] [xint] Fourth release, requesting preliminary review again

Subject: Re: [boost] [xint] Fourth release, requesting preliminary review again
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-06-03 14:04:52

Chad Nelson wrote:
> On 06/03/2010 09:40 AM, Marius Stoica wrote:
>
> > Maby you can do something like this :
> >
> > integer_t <
> >     throws<false>,
> >     size<128>, // 0 means unlimited
> >     thread_safe<false>> myint;
> >
> > You could also have some other policies
> >   -overflow policy( become nan, overflow to negative)
> >   -signed/unsigned policy
>
> I'm not sure that's really an improvement. The current design
> separates throwing and nonthrowing for a reason; take a look
> at some of the function implementations and you'll see why.
> Combining those would mean, at the very least, an extra if
> statement in every function.

What if the policy class provided the behavior you would otherwise control with a conditional?  For those policies in which the behavior is not needed, the inline, static member function would do nothing.  For those in which the behavior is needed, the member function would do the work unconditionally.  Changing the policy changes the behavior, so no need for a conditional.

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