RESOLVED FIXED 125323
Clean up the forwarding headers of RenderBlock.h
https://bugs.webkit.org/show_bug.cgi?id=125323
Summary Clean up the forwarding headers of RenderBlock.h
Zoltan Horvath
Reported 2013-12-05 16:48:21 PST
In this patch, I removed the unnecessary forwarding headers from RenderBlock.h, and moved some to RenderBlockFlow.h.
Attachments
Patch (2.48 KB, patch)
2013-12-05 17:30 PST, Zoltan Horvath
no flags
Zoltan Horvath
Comment 1 2013-12-05 17:30:28 PST
WebKit Commit Bot
Comment 2 2013-12-05 19:15:58 PST
Comment on attachment 218560 [details] Patch Clearing flags on attachment: 218560 Committed r160209: <http://trac.webkit.org/changeset/160209>
WebKit Commit Bot
Comment 3 2013-12-05 19:16:00 PST
All reviewed patches have been landed. Closing bug.
Darin Adler
Comment 4 2013-12-06 09:54:52 PST
(In reply to comment #0) > In this patch, I removed the unnecessary forwarding headers from RenderBlock.h, and moved some to RenderBlockFlow.h. For what it’s worth, the correct name for these is “forward declarations” rather than “forwarding headers”.
Zoltan Horvath
Comment 5 2013-12-06 10:17:15 PST
(In reply to comment #4) > For what it’s worth, the correct name for these is “forward declarations” rather than “forwarding headers”. Ah, sorry about the typo. I think removing forward declarations, which are not used anymore in that context, totally makes sense. Some of them weren't used in RenderBlock.h, but only in RenderBlockFlow.h, so moving these to their place makes the code cleaner, and makes easier to figure out what is going on, if you need to deal with them. The work that lead me to do this was about the RenderBlockLineLayout.cpp refactoring, when I tried to use a header as a header somewhere, but the cross-dependencies in the includes/include-orders made it difficult.
Darin Adler
Comment 6 2013-12-06 10:26:15 PST
Change was great; I am 100% happy with this patch. I was commenting the terminology you were using so you could be clearer next time.
Zoltan Horvath
Comment 7 2013-12-06 10:29:57 PST
(In reply to comment #6) > Change was great; I am 100% happy with this patch. I was commenting the terminology you were using so you could be clearer next time. Thanks for the clarification! I'll pay more attention to use the right terminology next time.
Note You need to log in before you can comment on or make changes to this bug.