[Webkit-unassigned] [Bug 62242] Compiling Chromium port under GCC 4.6 produces warnings about nullptr

[bugzilla-daemon at webkit.org]

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





--- Comment #5 from Ryan Sleevi <rsleevi at chromium.org>  2011-06-07 16:02:48 PST ---
Nico: If you check the header file, it's actually setup to use the c++0x symbol when compiling in c++0x. However, if --std=c++0x wasn't passed (for GCC), then it falls back to implementing an equivalent functionality (in the std:: namespace, which is technically undefined)

The issue is GCC 4.6 doesn't realize that the code *is* setup for c++0x compilation already, and thus emits the warning in non-c++0x mode.

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