"Beman Dawes" wrote:
There is an early version of Boost.System stuff in the vault. Go to the System directory at http://boost-consulting.com/vault/ for system-0.1.zip.
The preliminary error_code/system_error docs can be viewed online at http://mysite.verizon.net/beman/system_error.html
The catch (...) in what() doesn't make much sense - the app would be likely terminated at the moment. A fixed size char[] array could be used w/o danger of throwing (as it is in STLport). Perhaps individual, platform dependent exceptions for relevant errors would be even more handy for users, ala: class system_error_ERROR_WRITE_PROTECT : public system_error Number of such miniclasses would be limited, the classes could be added as needed, fallback will always exist Portable applications would use only the base. The few classes where the error means the same on all platforms (Win32: ERROR_FILE_NOT_FOUND, errno: ENOFILE) could have common parent. ------------ In process_exec.hpp two handles leak if timeout expires. The thread handle could be closed immediatelly after process starts. /Pavel