[fdo-dev] Standard exceptions handling practice

Greg Boone greg.boone at autodesk.com
Fri Sep 1 10:56:01 EDT 2006

When dealing with 3rd party exceptions, we try our *best* to catch these
exceptions in the provider code base and translate the contents of the
exception into an FdoException. We then throw the FdoException. Our main
clients such as Map and MapGuide are set up to catch instances of
FdoException when executing FDO logic and allowing other exceptions to
be thrown when executing provider code could severely compromise their
error handling strategies.


-----Original Message-----
From: Mateusz Loskot [mailto:mateusz at loskot.net] 
Sent: Thursday, August 31, 2006 11:40 PM
To: dev at fdo.osgeo.org
Subject: [fdo-dev] Standard exceptions handling practice


As I see, FDO uses non-standard exceptions.
What is the recommended practice in FDO [1] to handle
standard exceptions?
For example, when using some operations from C++ Standard Library or
Boost that may throw exception (standard exception),
how should I handle them in FDO code?
Am I supposed to convert every standard exception to one of the FDO
exception and re-thrown?

[1] I use FDO to name all FDO projects and their sources,
not only fdocore.

Mateusz Loskot

To unsubscribe, e-mail: dev-unsubscribe at fdo.osgeo.org
For additional commands, e-mail: dev-help at fdo.osgeo.org

More information about the Fdo-internals mailing list