Bug 75664 - MASTER: Move WebCore/platform into its own Platform directory
Summary: MASTER: Move WebCore/platform into its own Platform directory
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 110330 75653 75663 75674
Blocks: 21354
  Show dependency tree / graph
 
Reported: 2012-01-05 15:42 PST by Eric Seidel (no email)
Modified: 2013-02-20 06:48 PST (History)
10 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Seidel (no email) 2012-01-05 15:42:51 PST 
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
Comment 1 James Robinson 2012-01-05 17:00:32 PST 
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).