Re: [boost] [system][filesystem v3] Question about error_codearguments

Subject: Re: [boost] [system][filesystem v3] Question about error_codearguments
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2009-10-27 09:53:00

Peter Foelsche wrote:
> "Christopher Kohlhoff" <chris_at_[hidden]> wrote in message
> news:1256082527.2327.1341115615_at_webmail.messagingengine.com...
>
> > The throwing overloads are most typically in small programs or at
> > program startup. Non-trivial programs will tend towards the second,
> > non-throwing overload. It is the nature of network applications to
> > react to errors as part of normal control flow, and
> > exception handling
> > is not a good approach for that.
>
> You are the author of the asio library in boost?
> With this kind of thinking, how did you get this position?

He got in this position by crafting, documenting, and submitting a highly useful and desirable library that the reviewing Boost community liked and accepted.

Did you raise your concerns during the review?  If so, they couldn't have been among the majority of opinions or the library wouldn't have been accepted.  If not, constructive criticism might lead to Asio improvements even now.

If you find the library so poorly designed and ill-conceived as to require starting from scratch, please submit your alternative.  If it is accepted and found to be superior to Asio, users will abandon Asio for your library and all will win (I'm sure Christopher would be happy to have his users write their programs with a better library if one was available).

Note that the options I've presented do not involve impugning Christopher's design skills or belittling the opinions of those that disagree with your viewpoint.  You will not make progress in this community if you persist in attacking.

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