| | 43 | == Boost.XML == |
| | 44 | |
| | 45 | I started a 'boost.xml' library (right now in https://svn.boost.org/svn/boost/sandbox/xml/) a long time ago, which I have never found enough time and energy to bring to a formal boost submission. |
| | 46 | Having a proper XML library as part of boost would be very useful, in particular if "proper XML" goes beyond the basics such as parsing. (There already are lots of half-baked XML parsers, but few fully conform to the spec, or yield well performing in-memory representations that can be traversed via XML-specific tools such as XPath.) |
| | 47 | |
| | 48 | === Prerequisites === |
| | 49 | |
| | 50 | The student needs to have at least a basic understanding of the XML and related spec, as well as some exposure to existing XML APIs (such as DOM, SAX, XMLReader) to understand the problem domain. |
| | 51 | |
| | 52 | == Boost.Python == |
| | 53 | |
| | 54 | There are a couple of independent improvements that may be done: |
| | 55 | |
| | 56 | - Add (better) support for !NumPy bindings. |
| | 57 | - Improve the converter registry to avoid conflicts when multiple extension modules try to expose the same C++ types. |
| | 58 | - Add bindings for other Python C API functions, such as exception handling. |
| | 59 | |
| | 60 | === Prerequisites === |
| | 61 | |
| | 62 | - Some basic Python knowledge (as well as !NumPy in the first case above). |
| | 63 | - Past experience with Boost.Python. |
| | 64 | |
| | 65 | |
