Delete Tracked, and move Location to its own file.

base/tracked_objects.h

 // Copyright (c) 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef BASE_TRACKED_OBJECTS_H_
 #define BASE_TRACKED_OBJECTS_H_
 #pragma once
 
 #include <map>
 #include <string>
 #include <vector>
 
 #include "base/base_export.h"
+#include "base/location.h"
+#include "base/time.h"
 #include "base/synchronization/lock.h"
-#include "base/tracked.h"
 #include "base/threading/thread_local_storage.h"
 
+// TODO(ajwong): Fix this comment to remove references to Tracked.

[willchan no longer on Chromium, 2011/09/13 05:06:56]

You gonna do this?

[awong, 2011/09/13 19:39:04]

Yep...sorry...apparently uploaded a stale CL. :(

I've fixed up the comment, and also fixed traced_object_unittest.cc .  If those
look good, I'll just try to propagate all the compile fixes and commit.

 // TrackedObjects provides a database of stats about objects (generally Tasks)
 // that are tracked.  Tracking means their birth, death, duration, birth thread,
 // death thread, and birth place are recorded.  This data is carefully spread
 // across a series of objects so that the counts and times can be rapidly
 // updated without (usually) having to lock the data, and hence there is usually
 // very little contention caused by the tracking.  The data can be viewed via
 // the about:tasks URL, with a variety of sorting and filtering choices.
 //
 // These classes serve as the basis of a profiler of sorts for the Tasks system.
 // As a result, design decisions were made to maximize speed, by minimizing
@@ skipping 112 matching lines @@
 // snapshot instances, and are used to print sub-totals in an about:tasks page.
 //
 // TODO(jar): I need to store DataCollections, and provide facilities for taking
 // the difference between two gathered DataCollections.  For now, I'm just
 // adding a hack that Reset()'s to zero all counts and stats.  This is also
 // done in a slighly thread-unsafe fashion, as the reseting is done
 // asynchronously relative to ongoing updates, and worse yet, some data fields
 // are 64bit quantities, and are not atomicly accessed (reset or incremented
 // etc.).  For basic profiling, this will work "most of the time," and should be
 // sufficient... but storing away DataCollections is the "right way" to do this.
-//
+
 class MessageLoop;
 
-
 namespace tracked_objects {
 
 //------------------------------------------------------------------------------
 // For a specific thread, and a specific birth place, the collection of all
 // death info (with tallies for each death thread, to prevent access conflicts).
 class ThreadData;
 class BASE_EXPORT BirthOnThread {
  public:
   explicit BirthOnThread(const Location& location);
 
@@ skipping 502 matching lines @@
   };
   static State state_;
 
   DISALLOW_COPY_AND_ASSIGN(AutoTracking);
 };
 
 
 }  // namespace tracked_objects
 
 #endif  // BASE_TRACKED_OBJECTS_H_