1This being an incomplete enumeration of things that would be nice to
2have in SDTS++.  If you would like to work on one of these, please
3send e-mail to sdts_software-owner@mailrmon1.er.usgs.gov saying so to
4insure that you're not duplicating someone else's efforts.
5
6
71. Better and more robust error handling
8
9	Possibly something as simplistic as iostream's error handling
10scheme.  For example, a reader could be in either a good(), bad(), or
11fail() state.  Nice, but a bit parsiminous on error reporting.
12
13        Note that an sio_Error mix-in class has been added; it needs
14to be brought in to some of the classes, namely the top level classes
15(i.e., sio_Reader and sio_Writer).
16
17
182. The I/O subsystem is in dire need of some re-design and re-implementation
19
20   - eliminate use of C-style mem*() functions in converters
21   - prefer use of references to pointers in converters
22   - replace sio_Buffer and vector<char> with ios::streambuf for speed-up
23   - rename converter member functions to something less confusing
24   - ...
25
263. For logical layer, these need to be implemented:
27
28   Link
29
30   Circular arc, three point center
31   Elliptical arc
32   Uniform B-spline
33   Piecewise Bezier
34
35   Ring with mixed composition
36   Ring composed of arcs
37
38   However the arc types aren't used in most SDTS transfer, so there's
39   no pressing need to implement those.
40
414. Replace use of ``sysutils'' package with boost filesystem
42