[fdo-dev] Assertions

Greg Boone greg.boone at autodesk.com
Mon Aug 14 17:45:52 EDT 2006

I am not sure what you mean by equality. All I am saying is that
generally, FDO does not throw assertions (except the CPPUNIT unit test
ASSERT macros).

This is because:

1) Assertions only are executed only in Debug and do not provide any
contextual error information to our users in a production environment
2) Assertions on Windows cause the execution of code to halt and force
the user to intervene. This cause some difficulty in automating the
execution of Debug unit tests in a CPPUNIT style framework


-----Original Message-----
From: Mateusz Loskot [mailto:mateusz at loskot.net] 
Sent: Monday, August 14, 2006 5:10 PM
To: dev at fdo.osgeo.org
Subject: Re: [fdo-dev] Assertions

Greg Boone wrote:
> In general the rule is not to use assertions in FDO code.
> The general rule is to throw an exception.


Do I understand you correctly that FDO puts equality
operator between assertions and exceptions?
If this is the case, I'm surprised.

Best regards
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