Use scoped_ptr in Files-map and remove unused functions

net/tools/flip_server/mem_cache.h

Index: net/tools/flip_server/mem_cache.h
diff --git a/net/tools/flip_server/mem_cache.h b/net/tools/flip_server/mem_cache.h
index d35322a1c57122e79647f095ae4b3b88ee78d535..6b85149eca0e804e6447f72f6a3a730e152c35f2 100644
--- a/net/tools/flip_server/mem_cache.h
+++ b/net/tools/flip_server/mem_cache.h
@@ -114,14 +114,12 @@ class MemCacheIter {
 
 class MemoryCache {
  public:
-  typedef std::map<std::string, FileData*> Files;
+  using Files = std::map<std::string, scoped_ptr<FileData>>;

[Ryan Hamilton, 2015/12/28 15:06:30]

Is there any reason to prefer using here to typedef?

[Avi (use Gerrit), 2015/12/28 15:09:43]

It's the new hotness as it's much easier to read and reason about.

http://chromium-cpp.appspot.com/ says about "using" : "Use instead of typedef,
unless the header needs to be compatible with C."

[Ryan Hamilton, 2015/12/28 18:23:25]

Definitely happy to follow the style guide, so +1 on this change. That being
said, just for my understanding is there any difference between:

  typedef old_type new_type;

and

  using new_type = old_type;

or are the synonymous? There is so much new hotness in C++11 that I'm not on top
of all of it :>

 
  public:
   MemoryCache();
   virtual ~MemoryCache();
 
-  void CloneFrom(const MemoryCache& mc);
-
   void AddFiles();
 
   // virtual for unittests
@@ -140,7 +138,6 @@ class MemoryCache {
 
  private:
   void InsertFile(FileData* file_data);
-  void ClearFiles();
 
   Files files_;
   std::string cwd_;