On Fri, 12 Feb 2010 14:38:18 +0100
Philipp Lohmann <[email protected]> wrote:

> The obvious optimization for that process would be leaving things as 
> they are and introduce an OSL_ASSERT_ABORT for those who really want
> that.

still one would need:
- to get rid of DBG_ASSERT, because it makes absolutely no sense to
  have both DBG_ASSERT and OSL_ASSERT).
- to move all the non-informal assertions up to OSL_ASSERT_ABORT. And
  Frank and Christian should be the first to do that for their
  assertions, if those are, as they claim, only reporting seriously
  messed up internal state unlike those chatty noncritical
  observations us other devs seem to use assertions for.

BR,

Bjoern


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

  • Re: [dev] Should as... bjoern michaelsen - Sun Microsystems - Hamburg Germany
    • Re: [dev] Shou... Frank Schoenheit, Sun Microsystems Germany
    • Re: [dev] Shou... Christian Lippka
      • Re: [dev] ... Malte Timmermann
        • Re: [d... bjoern michaelsen - Sun Microsystems - Hamburg Germany
          • Re... Christian Lippka
          • Re... Rich
          • Re... bjoern michaelsen - Sun Microsystems - Hamburg Germany
            • ... Philipp Lohmann
              • ... bjoern michaelsen - Sun Microsystems - Hamburg Germany
              • ... Philipp Lohmann
              • ... Frank Schoenheit, Sun Microsystems Germany
              • ... Ingrid Halama
              • ... Christian Lippka
              • ... bjoern michaelsen - Sun Microsystems - Hamburg Germany
              • ... Ingrid Halama
              • ... Frank Schoenheit, Sun Microsystems Germany
          • Re... Frank Schoenheit, Sun Microsystems Germany
            • ... Terrence Enger
      • Re: [dev] ... Stephan Bergmann

Reply via email to