Add accessor for can_wake_from_suspend_ in AlarmTimer

components/timers/alarm_timer.h

 // Copyright 2014 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 COMPONENTS_TIMER_ALARM_TIMER_H_
 #define COMPONENTS_TIMER_ALARM_TIMER_H_
 
 #include "base/callback.h"
 #include "base/macros.h"
 #include "base/memory/ref_counted.h"
@@ skipping 54 matching lines @@
   void Stop() override;
   void Reset() override;
 
   // MessageLoop::DestructionObserver overrides.
   void WillDestroyCurrentMessageLoop() override;
 
   // Must be called by the delegate to indicate that the timer has fired and
   // that the user task should be run.
   void OnTimerFired();
 
+  bool can_wake_from_suspend() { return can_wake_from_suspend_; }

[Daniel Erat, 2014/10/30 02:51:21]

nit: i think that inline methods usually come right after the d'tor in chromium
(i usually put overrides at the end of the public section too)

[Chirantan Ekbote, 2014/10/30 20:41:37]

Done.

+
  private:
   // Initializes the timer with the appropriate delegate.
   void Init();
 
   // Delegate that will manage actually setting the timer.
   scoped_refptr<Delegate> delegate_;
 
   // Keeps track of the user task we want to run.  A new one is constructed
   // every time Reset() is called.
   scoped_ptr<base::PendingTask> pending_task_;
 
   // Tracks whether the timer has the ability to wake the system up from
   // suspend.  This is a runtime check because we won't know if the system
   // supports being woken up from suspend until the delegate actually tries to
   // set it up.
   bool can_wake_from_suspend_;
 
   // Pointer to the message loop that started the timer.  Used to track the
   // destruction of that message loop.
   base::MessageLoop* origin_message_loop_;
 
   base::WeakPtrFactory<AlarmTimer> weak_factory_;
 
   DISALLOW_COPY_AND_ASSIGN(AlarmTimer);
 };
 
 }  // namespace timers
 
 #endif  // COMPONENTS_TIMER_ALARM_TIMER_H_