Introduced new scheme for controlling the functionality inside the audio processing module

webrtc/modules/audio_processing/level_controller/level_controller.cc

Index: webrtc/modules/audio_processing/level_controller/level_controller.cc
diff --git a/webrtc/modules/audio_processing/level_controller/level_controller.cc b/webrtc/modules/audio_processing/level_controller/level_controller.cc
index 2294396607505f86511e83f12f110a8a636601bf..7096f2c4bb2abd248bd0457fa8863819e1d55cfc 100644
--- a/webrtc/modules/audio_processing/level_controller/level_controller.cc
+++ b/webrtc/modules/audio_processing/level_controller/level_controller.cc
@@ -72,6 +72,10 @@ const int kMetricsFrameInterval = 1000;
 
 }  // namespace
 
+bool AudioProcessing::Config::LevelController::Validate() const {

[the sun, 2016/08/30 18:05:35]

How about a static function in LevelController instead:

bool LevelController::Validate(const
AudioProcessing::Config::LevelControllerConfig& config) {
?

That will be easy to change into
bool LevelController::Validate(const LevelController::Config& config) {
once we get there.

Adding the function definition here, of something declared in AudioProcessing,
is confusing, and likely validates the style guide (or it should).

[peah-webrtc, 2016/08/31 08:08:32]

That sounds good!
Done.

+  return true;
+}
+
 int LevelController::instance_count_ = 0;
 
 void LevelController::Metrics::Initialize(int sample_rate_hz) {