<div dir="ltr">On Wed, Mar 18, 2015 at 9:43 PM, Myles C. Maxfield <span dir="ltr"><<a href="mailto:mmaxfield@apple.com" target="_blank">mmaxfield@apple.com</a>></span> wrote:<div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I’d like to announce that I intend to create a standalone static library from the current contents of WebCore/platform over the coming months. This will involve creating a “Platform" top-level directory and moving source files into it, one by one.<br></blockquote><div><br></div><div>That sounds great.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
There are a few reasons for this:<br>
<br>
1. Enforcing the layering between Platform and WebCore. Moving Platform into its own target/directory can guarantee that nothing inside it knows about anything in WebCore.<br>
2. Being able to test code in the Platform directory with TestWebKitAPI (without exporting Platform symbols from the WebCore library)<br></blockquote><div><br></div><div>We should make sure unit tests we write for the Platform API doesn't reduce the hackability / refactor-ability of the code. It's very easy to write a lot of unit tests around an internal API that prevent large architectual changes. Just look at webkitpy! It's impossible to hack on that codebase due to thousands of unit tests that depend on non-public API.</div><div><br></div><div>- R. Niwa</div><div><br></div></div></div></div>