Quoting Stephen torri ([EMAIL PROTECTED]): | I believe that asserts should be eliminated. They only cause the program | to 'Abort' and not give you any reason for why.
As other people have replied, ASSERTs in Crypto++ catches programming errors, indicating you've used the library incorrectly. Such mistakes shold be caught during testing before releasing your code. Ideally, your code should be so well-tested that it would never abort in any given (practical) runtime-situation. If you've done this, and especially for embedded devices, you could possibly even remove ASSERTs in the release version. | As a professor I know at Vanderbilt says where is stdout on a missle? A good point that code should be properly tested. Apropos, many UNIX daemons close their stdout and stderr filehandles, since they should be performing their tasks silently and invisibly, or at least give reports using alternative channels (such as e.g. syslog). -- Christian Stigen Larsen -- http://csl.sublevel3.org -- mob: +47 98 22 02 15
