bjoern michaelsen - Sun Microsystems - Hamburg Germany wrote:
On Fri, 12 Feb 2010 12:43:29 +0100
Malte Timmermann <malte.timmerm...@sun.com> wrote:
-1 for discussing here whether or not QA should use non-pros, because
it IMHO has absolutely no influence on how assertions should behave.
And if you want QA to use non-pros, they for sure would give up quite
soon when assertions always abort.
With assertions being assertions and "give up" meaning reporting it,
thats exactly the desired behavior.
nope. not meaning that for sure. "give up" means stop using anything but
some older, proven to be stable, version. just like me.
make development versions hard or impossible to use, and nobody will.
also, i think question whether qa should use non-prod builds is very on
topic - this decision will pretty much determine that.
Current situation:
- assertions might be anything from a informal "I didnt expect this
external data" to a critical "internal state corrupt"
Desired situation:
- assertions are only "internal state corrupt" messages and should
abort
- everything else is tracing, logging
For example, Frank is claiming his asserts are all serious issues and
thus shouldnt be "degraded" to mere traces. So keeping "his" asserts as
assertions, even if they abort should not scare anyone, right?
Best Regards,
Bjoern
--
Rich
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
