Hi Martin, > Unfortunately they will also get assertions with a vanilla build, > which makes this less useful. I wasted a lot of time trying to > track down the cause of an assertion, assuming it was due to a > change I had introduced, before discovering it still occurred > with a clean checkout.
Unfortunately, not all developers pay attention to assertion nowadays. Means developers working on product builds might silently introduce assertions which then annoy others working with the non-products. So, if you strive for using non-product builds - and I'm constantly lobbying for doing so, since experience tells that a certain class of problems can be found much earlier, if you just believe the assertions -, you should always have a "normal" build at hand, to verify the assertions you see are not introduced by your changes. 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]
