Hi,
Ok, I just commited the modifs to check compression version and abort
with an explicit message if there is a mismatch. This will avoid
unexplicit errors like the core Vadim found.
However, I don't happen to have any older db's so, if someone can
check if it aborts correctly with good error messages.
Uh, by the ways, in my code, when an "assert" fails I print an error
message and force a core dump (*NULL=0). So don't panic if there is a
core dump after an error message. This is for debuging purposes (gdb).
This is certainly NOT a good way to do things in a released version!
* How are catastrophic errors supposed to be dealt with in htdig?
* This leads to a bigger question of error processing.... is the
standard C++ error mechanism portable enough to be used?
Cheers,
Marcel.
----------------------
Marcel Bosc
ECILA
100 av. du Gal Leclerc
93500 Pantin - France
Tel: 33 1 56 96 10 85
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
