Boost logo

Boost :

Subject: Re: [boost] [process] Arguments and Context concepts
From: vicente.botet (vicente.botet_at_[hidden])
Date: 2011-01-23 13:10:44

----- Original Message -----
From: "Jeff Flinn" <TriumphSprint2000_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Sunday, January 23, 2011 4:29 PM
Subject: Re: [boost] [process] Arguments and Context concepts

> Boris Schaeling wrote:
>> On Fri, 21 Jan 2011 08:21:56 +0100, vicente.botet
>> <vicente.botet_at_[hidden]> wrote:
> ...
>>> [...]
>>>> Well, you might not have access to the source code for example and can't
>>>> make the child process change the working directory.
>>> This is too specific to be included in a Process library.
>> I find this a very subjective argument. If we leave everything out
>> someone finds too specific there is probably nothing left. :-)
> A more tangible argument is that the working directory must be set to
> the location of the to-be-exec'd executable for Mac OSX to properly
> launch a child process. It would be difficult to have the calling
> application change the directory and change it back as currently the
> posix fork/exec paradigm is not synchronous.

Boost.Process don't needs a specific work_dir to be able to do it.
Shouldn't Boost.Process do it transparently without the user been forced to change the work_dir on the Context.?


Boost list run by bdawes at, gregod at, cpdaniel at, john at