explicit use of std::vector instead of buffer/Buffer
There were several scoped 'using buffer = std::vector<uint8_t>;' in
header files. This consolidates the code base to use
std::vector<uint8_t> instead of buffer or Buffer. This makes the code
easier to read and debug.
Change-Id: I918a0f6ca9b8e4b9d331175dccff45cbf4c8379d
Signed-off-by: Vernon Mauery <vernon.mauery@linux.intel.com>
diff --git a/socket_channel.hpp b/socket_channel.hpp
index 2bc7a33..5996b62 100644
--- a/socket_channel.hpp
+++ b/socket_channel.hpp
@@ -10,7 +10,6 @@
namespace udpsocket
{
-using buffer = std::vector<uint8_t>;
/** @class Channel
*
* @brief Provides encapsulation for UDP socket operations like Read, Peek,
@@ -79,7 +78,7 @@
* In case of error, the return code is < 0 and vector is set
* to size 0.
*/
- std::tuple<int, buffer> read();
+ std::tuple<int, std::vector<uint8_t>> read();
/**
* @brief Write the outgoing packet
@@ -92,7 +91,7 @@
* @return In case of success the return code is 0 and return code is
* < 0 in case of failure.
*/
- int write(buffer& inBuffer);
+ int write(const std::vector<uint8_t>& inBuffer);
/**
* @brief Returns file descriptor for the socket