Bug 75664
| Summary: | MASTER: Move WebCore/platform into its own Platform directory | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Eric Seidel (no email) <eric> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | abarth, cdumez, jamesr, jesus, kenneth, laszlo.gombos, luiz, mikhail.pozdnyakov, noam, tmpsantos |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | 110330, 75653, 75663, 75674 | ||
| Bug Blocks: | 21354 | ||
Eric Seidel (no email)
Move WebCore/platform into its own Platform namespace
This will help detect and prevent layering violations, as using WebCore:: from within platform/ will be disallowed.
This is an incremental step towards moving Platform into its own separate module, as discussed in:
https://lists.webkit.org/pipermail/webkit-dev/2011-December/018899.html
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
James Robinson
Based on IRC discussion it might be useful to move code into Source/Platform but leave it in the WebCore namespace. Having a separate directory and include paths will let us enforce strict dependency ordering, as code in Source/Platform/ will not have any paths in Source/WebCore/* on its include path, but leaving it in the WebCore namespace can ease the transition. Retitling bug to be more general (even if we change the namespaces of things we will definitely also change the directory).