[Webkit-unassigned] [Bug 51122] New: Assigning 0 to a RefPtr<> confuses Visual Studio 2010

[bugzilla-daemon at webkit.org]

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

           Summary: Assigning 0 to a RefPtr<> confuses Visual Studio 2010
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Windows Vista
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebKit Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: jeanluc at chromium.org


When faced with:
       RefPtr<Node> node;
       node = 0;
the VS2010 compiler can't tell whether to cast the integral 0 to nullptr_t or to T*, e.g. to use either
       RefPtr& operator=(T*);
       RefPtr& operator=(std::nullptr_t) { clear(); return *this; }

If we intend WebKit to track C++ 0x, changing the assignments to use nullptr would be forward thinking.    If not,  #ifdef out "operator=(std::nullptr_t)" might be a solution, but I have not looked closely at the code to see the implications.

Note that VS2010 does not currently support __has_feature().

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