Re: [boost] [gsoc] Boost.Process done

Subject: Re: [boost] [gsoc] Boost.Process done
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-09-01 10:44:52

Ilya Sokolov wrote:
> On 01.09.2010 14:51, Stewart, Robert wrote:
>
> > there was some mention of using boost::filesystem::path, IIRC,
> > so the dependency exists independent of that error type.
>
> "some mention of using boost::filesystem::path" doesn't mean
> that "the dependency exists independent of that error type".

Certainly.  My using "some mention" was because I thought I'd read something about path being used already, not that it was a suggestion mentioned in passing.  That's why I used "IIRC."

I was implying that if, indeed, path is used elsewhere -- and I don't know that -- then there is already a dependency.  I was also allowing for the possibility that if path will appear soon in an update, if indeed it isn't used presently, the dependency would arise at that time and justify using the error type now.  Only in the case that path is not used now and isn't used in an upcoming update does the error type remain a problem.

It is good to avoid new exception types when reasonable.  If there is no other reason to depend upon Boost.Filesystem -- Jeff Flynn has suggested there is -- another exception type is certainly appropriate.

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