/usr/include/boost/process
NameSizeModeActions
detail/-0755rm
args.hpp89680644editdlrm
async.hpp36830644editdlrm
async_pipe.hpp76940644editdlrm
async_system.hpp45350644editdlrm
child.hpp53090644editdlrm
cmd.hpp30720644editdlrm
env.hpp123010644editdlrm
environment.hpp247580644editdlrm
error.hpp66570644editdlrm
exception.hpp7100644editdlrm
exe.hpp25360644editdlrm
extend.hpp145850644editdlrm
group.hpp67600644editdlrm
handles.hpp30380644editdlrm
io.hpp199900644editdlrm
locale.hpp69680644editdlrm
pipe.hpp187630644editdlrm
posix.hpp28480644editdlrm
search_path.hpp17750644editdlrm
shell.hpp25890644editdlrm
spawn.hpp19290644editdlrm
start_dir.hpp34490644editdlrm
system.hpp40930644editdlrm
windows.hpp36750644editdlrm
Edit: /usr/include/boost/process/async.hpp (3683B)
// Copyright (c) 2016 Klemens D. Morgenstern // // Distributed under the Boost Software License, Version 1.0. (See accompanying // file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) /** \file boost/process/async.hpp The header which provides the basic asynchrounous features. It provides the on_exit property, which allows callbacks when the process exits. It also implements the necessary traits for passing an boost::asio::io_context, which is needed for asynchronous communication. It also pulls the [boost::asio::buffer](http://www.boost.org/doc/libs/release/doc/html/boost_asio/reference/buffer.html) into the boost::process namespace for convenience. \xmlonly namespace boost { namespace process { unspecified buffer; unspecified on_exit; } } \endxmlonly */ #ifndef BOOST_PROCESS_ASYNC_HPP_ #define BOOST_PROCESS_ASYNC_HPP_ #include #include #include #include #include #include #include #if defined(BOOST_POSIX_API) #include #include #include #include #elif defined(BOOST_WINDOWS_API) #include #include #include #include #endif namespace boost { namespace process { namespace detail { struct async_tag; template struct is_io_context : std::false_type {}; template<> struct is_io_context : std::true_type {}; template inline asio::io_context& get_io_context(const Tuple & tup) { auto& ref = *boost::fusion::find_if>(tup); return ref.get(); } struct async_builder { boost::asio::io_context * ios; void operator()(boost::asio::io_context & ios_) {this->ios = &ios_;}; typedef api::io_context_ref result_type; api::io_context_ref get_initializer() {return api::io_context_ref (*ios);}; }; template<> struct initializer_builder { typedef async_builder type; }; } using ::boost::asio::buffer; #if defined(BOOST_PROCESS_DOXYGEN) /** When an io_context is passed, the on_exit property can be used, to be notified when the child process exits. The following syntax is valid \code{.cpp} on_exit=function; on_exit(function); \endcode with `function` being a callable object with the signature `(int, const std::error_code&)` or an `std::future`. \par Example \code{.cpp} io_context ios; child c("ls", ios, on_exit=[](int exit, const std::error_code& ec_in){}); std::future exit_code; chlid c2("ls", ios, on_exit=exit_code); \endcode \note The handler is not invoked when the launch fails. \warning When used \ref ignore_error it might get invoked on error. \warning `on_exit` uses `boost::asio::signal_set` to listen for `SIGCHLD` on posix, and so has the same restrictions as that class (do not register a handler for `SIGCHLD` except by using `boost::asio::signal_set`). */ constexpr static ::boost::process::detail::on_exit_ on_exit{}; #endif }} #endif /* INCLUDE_BOOST_PROCESS_DETAIL_ASYNC_HPP_ */