| 12 | | == Some Library == |
| 13 | | === Idea 1 === |
| 14 | | === Idea 2 === |
| | 12 | == Boost.Process == |
| | 13 | |
| | 14 | A first version of Boost.Process was created in the SoC 2006 program (see http://code.google.com/soc/2006/boost/appinfo.html?csaid=7ADC016A60772A9C). Since then there have been several attempts to finish this library (one by myself in 2009). While there is considerable interest in this library noone had the time yet to do the job. |
| | 15 | |
| | 16 | The status quo of the library (which is available at http://svn.boost.org/svn/boost/sandbox/process/) is documented at http://www.highscore.de/cpp/process/. There have been various discussions in the Boost mailing lists last year, too. |
| | 17 | |
| | 18 | As far as I remember some problems are: |
| | 19 | |
| | 20 | * As platforms are very different when it comes to supporting higher level features it's not entirely clear how the architecture should look like (there have been different implementations in the past). |
| | 21 | * Some parts of the library could become libraries of their own or even be moved to other libraries like Boost.Interprocess (eg. pipes). |
| | 22 | * Supporting asynchronous I/O works already but doesn't really follow Boost.Asio patterns. |
| | 23 | * Unit tests are different than in other libraries (as processes have to be created) and have to be improved. |
| | 24 | |
| | 25 | The goal would be to finish the library after 4 years that it can finally be reviewed. ;) |
| | 26 | |
| | 27 | Boris, boris@highscore.de |
