[Webkit-unassigned] [Bug 27980] Give an ability to WebKit to free statically allocated pointers before quit

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Oct 27 12:03:09 PDT 2009


--- Comment #44 from Darin Adler <darin at apple.com>  2009-10-27 12:03:07 PDT ---
(In reply to comment #43)
> So can DEFINE_STATIC_LOCAL still eventually be removed once we no longer
> support this broken version of Apple's GCC?  Or does this new usage make us
> forever dependent on this macro?

I don't think removing DEFINE_STATIC_LOCAL is a good idea, regardless of this
new usage. It's true that we use it to work around a GCC bug. But we also use
it to make indicate the idiom of using a local variable in a way that avoids
static destructors. It's better to that than to handwrite the idiom each time.

We might want to rename it, but it seems unlikely we'd want to remove it.

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

More information about the webkit-unassigned mailing list