RESOLVED FIXED91847
[chromium] Don't include WebCore headers in TestInterfaces so it's safe to include from outside of WebCore
https://bugs.webkit.org/show_bug.cgi?id=91847
Summary [chromium] Don't include WebCore headers in TestInterfaces so it's safe to in...
jochen
Reported 2012-07-20 03:00:01 PDT
[chromium] Don't include WebCore headers in TestInterfaces so it's safe to include from outside of WebCore
Attachments
Patch (3.60 KB, patch)
2012-07-20 03:07 PDT, jochen
no flags
jochen
Comment 1 2012-07-20 03:07:02 PDT
Adam Barth
Comment 2 2012-07-20 08:38:54 PDT
Comment on attachment 153462 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=153462&action=review > Tools/DumpRenderTree/chromium/TestRunner/TestInterfaces.h:48 > + class Internal; > + Internal* m_internal; Isn't there an OwnPtr-like class we can use from the WebKit API? WebPrivatePtr or something?
jochen
Comment 3 2012-07-20 10:59:25 PDT
(In reply to comment #2) > (From update of attachment 153462 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=153462&action=review > > > Tools/DumpRenderTree/chromium/TestRunner/TestInterfaces.h:48 > > + class Internal; > > + Internal* m_internal; > > Isn't there an OwnPtr-like class we can use from the WebKit API? WebPrivatePtr or something? Yes, but it would require defining WEBKIT_IMPLEMENTATION in TestInterfaces.cpp, and in contrast to OwnPtr, it doesn't destroy it's pointee automatically on destruction I esp. don't like defining WEBKIT_IMPLEMENTATION, wdyt?
Adam Barth
Comment 4 2012-07-20 11:02:38 PDT
We don't want to define WEBKIT_IMPLEMENTATION since this library isn't part of webkit.dll. Lets try your approach for now. We might need to revise the approach in the future.
WebKit Review Bot
Comment 5 2012-07-20 11:13:33 PDT
Comment on attachment 153462 [details] Patch Clearing flags on attachment: 153462 Committed r123240: <http://trac.webkit.org/changeset/123240>
WebKit Review Bot
Comment 6 2012-07-20 11:13:37 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.