-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I am currently going through the code to try to fix the functions that
should return UT_Error but instead return UT_Bool. (There are lots) In
doing this, I have two potential new errors -
1 UT_FAKEOK - This would represent an OK that didn't mean anything, as in,
there was only one return statment, and it returned OK. This has a
serious boolean testing problem (0 is taken), and cannot be implemented if
that is not solved.
2 UT_REALLY_BAD_ERROR - This would go along with
UT_ASSERT(UT_SHOULD_NOT_HAPPEN). The code would look like
if(fatalErrorHasOccured)
{
UT_ASSERT(UT_SHOULD_NOT_HAPPEN);
return UT_REALLY_BAD_ERROR;
}
This might well be superfluous.
Neither of these is really neccessary, but I just wanted to see what
people thought of them.
sam th
[EMAIL PROTECTED]
http://bur-jud-118-039.rh.uchicago.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE44tGqt+kM0Mq9M/wRAib5AJ9ts52HVSesbesV1bpPaCqF79au0wCfapOo
lrQ2OQqLxOqDbbdOL0LwUoo=
=LCJQ
-----END PGP SIGNATURE-----
