Bug 48505

Summary: Change Noncopyable macro to avoid using two subsequent line
Product: WebKit Reporter: Zoltan Horvath <zoltan>
Component: Web Template FrameworkAssignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Normal CC: darin
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: All   
Bug Depends on: 46589    
Bug Blocks:    
Attachments:
Description Flags
proposed patch darin: review-

Zoltan Horvath
Reported 2010-10-28 03:38:28 PDT
With the actual WTF_MAKE_NONCOPYABLE and WTF_MAKE_FAST_ALLOCATED macro implementations when a class needs to be Noncopyable and FastAllocated as well we'd have needed to add 2 subsequent line 1-1 for each macro. With this change we can use these in one line. Examples: In the case when Example is not instantiated by new and needs to be Noncopyable: class Example { WTF_MAKE_NONCOPYABLE(Example); }; In the case when Example is instantiated by new and needs to be Noncopyable: class Example { WTF_MAKE_NONCOPYABLE(Example, WTF_MAKE_FAST_ALLOCATED); };
Attachments
proposed patch (2.14 KB, patch)
2010-10-28 03:39 PDT, Zoltan Horvath
darin: review-
Zoltan Horvath
Comment 1 2010-10-28 03:39:45 PDT
Created attachment 72166 [details] proposed patch
Zoltan Horvath
Comment 2 2010-11-02 08:41:35 PDT
This is ping for review.
Darin Adler
Comment 3 2010-11-03 10:29:36 PDT
Comment on attachment 72166 [details] proposed patch This doesn’t seem like an improvement to me. Just seems a bit strange. If we want to put things all on one line, we can do that without adding this unusual feature to the macro. WTF_MAKE_NONCOPYABLE(Example); WTF_MAKE_FAST_ALLOCATED; I suggest not making this change.
Zoltan Horvath
Comment 4 2010-11-04 00:44:00 PDT
Right! I close the bug as invalid.
Note You need to log in before you can comment on or make changes to this bug.