TODO Items

This page contains a list of items that may be implemented for future EDoc++ releases. This list is a cut-down version of the TODO.txt file in CVS listing only some of the more useful or important items. If there is a particular feature or idea you wish to be included please send a message to the mailing list.

Have EDoc++ track API imports/exports and emit an error if an exported function throws an exception whose type is NOT exported.

EDoc++ currently does not take into account calls to set_unexpected() for its exception propagation calculations.

Tests fail on cygwin as python seems to have some problems with its thread support that is used by the testing framework.

Eithre submit patches upstream to doxygen to allow it to work with EDoc++ generated files, or create special documentation generator that places doxygen documentaiton inline with the source code so no special features are required by doxygen

Add ability to create output formatting plugins. Examples include: doxygen, simple-doxygen, simple, ... boost etc

Warn of exceptions that may be thrown while inside a destructor (Even if they do not propagate out of the destructor)

Make GCC Modification a plugin using the development GCC plugin branch instead of a patch against GCC.

Fix implementation so that the GCC modification will work with pre-compiled headers. (Big change to use GCC garbage collector instead of the current manual memory allocation scheme)

Allow user to document the originating exception at the point of the throw and export this to doxygen.

Update the GCC modification to ensure it will gracefully handle error mark nodes used to notify of compile errors.