Hi Bjoern, > I am one of the devs that rarely use a non-pro build, but not because > "it's unusable 'cause of the many assertions", but because there are > simply to many differences from the product build in them, causing > issues (first of all: annoying build breakers).
So you prefer not using them, and leave it to others to fix those? Really? > I do, however build with DEBUG=true to see assertions. This will only give you OSL assertions, not the tools-based ones, which still are the majority. Also, it only gives you the assertions from files you explicitly compile with this setting - i.e., if you use a component in a library which you did not compile with debug, and this component would report client errors via assertions, the you miss those, too. > On the topic of "what is an assertion": Yes, assertions should abort. > Otherwise, they are not an assertion, but something that is better > covered by OSL_TRACE. Sigh. Again: No matter how the term "assertion" is defined in theory, in practice there are *hundreds* or *thousands* of "assertions" (aka usages of DBG_*) which do not match the definition. Saying "Assertions should abort because otherwise they're not assertions" is, sorry, just closing your eyes against reality. Ciao Frank -- - Frank Schönheit, Software Engineer [email protected] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
