Update audio code to use size_t more correctly, webrtc/voice_engine/ portion.

webrtc/voice_engine/channel.h

Index: webrtc/voice_engine/channel.h
diff --git a/webrtc/voice_engine/channel.h b/webrtc/voice_engine/channel.h
index 398087eefb481a0cd96624b6b086c3d9c0acbe58..d6fddbe7b8abca0a1e4153a3a1e9a996e8f7823f 100644
--- a/webrtc/voice_engine/channel.h
+++ b/webrtc/voice_engine/channel.h
@@ -432,7 +432,7 @@ public:
     // does not go through transmit_mixer and APM.
     void Demultiplex(const int16_t* audio_data,
                      int sample_rate,
-                     int number_of_frames,
+                     size_t number_of_frames,

[henrika_webrtc, 2015/07/13 07:38:08]

It is not clear to me why size_t is required here. Can you provide some more
general background on why this sort of changes are done. I am sure that all is
OK; just want to understand and learn. Thanks.

[Peter Kasting, 2015/07/13 22:12:28]

Sure.  A fairly complete argument/set of tradeoffs can be found in the design
doc I wrote for a previous "use size_t more" change; see
https://docs.google.com/document/d/1I6nmE9D_BmCY-IoV6MDPY2V6WYpEI-dg2apWXTfZy...
.

If you want a short summary, basically the rule is "use size_t for object sizes
or lengths of containers in memory".  This matches how the STL works, is
approved by the Google style guide, promotes consistency of type usage, and can
sometimes simplify or clarify code by eliminating the possibility of certain
variables taking on negative values.

In this example, the actual frames are stored in memory, so we use a size_t to
count them.

[henrika_webrtc, 2015/07/14 07:54:09]

Thanks!

                      int number_of_channels);
     uint32_t PrepareEncodeAndSend(int mixingFrequency);
     uint32_t EncodeAndSend();