[Webkit-unassigned] [Bug 36527] Need an ASSERT that's enabled in release builds

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=36527





--- Comment #7 from Jeremy Orlow <jorlow at chromium.org>  2010-03-24 11:15:30 PST ---
(In reply to comment #6)
> If we think the word FATAL expresses this well, then I think we probably a name
> like FATAL_ERROR for something that invokes CRASH. I personally think we can
> live with only FATAL_ERROR, but I would not be strongly opposed to
> FATAL_ASSERT.
> 
> I think we need a brief note on the website explaining the proper use of these.
> I worry that they will be used too often.

Since both of you (Darins) are against this, I'm perfectly fine with us
dropping this.

But, if we do go ahead with this, I'd say that |FATAL_ERROR(some_expression);|
is less clearly an assertion than |FATAL_ASSERT(some_expression);|.

And where on the web page would be good for a note?

Anyone else have thoughts?  If no one else is in favor, maybe we should just
forget about this and continue with |if () CRASH;|

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.