Aarno Syv�nen wrote:
There actually seems to two kinds of panic:
a) Configuration errors. In this case, continuation really is impossible. b) Libs has some sanity checks that cause panic. If we just have a broken message, we must just ignore message, not panic.
thats right. That's how J�rg understands and "unnecessary" panic, since a broken message does not mean an broken internal operational state.
IMO, we should throw panics if we're unable to carry on with stable operation, otherwise dump error, discard whatever could not be done, and continue operation.
Hence +1 on autiting panics for recoverable states.
Stipe
mailto:stolj_{at}_wapme.de ------------------------------------------------------------------- Wapme Systems AG
Vogelsanger Weg 80 40470 D�sseldorf, NRW, Germany
phone: +49.211.74845.0 fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de http://www.wapme-systems.de/ -------------------------------------------------------------------
