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.cpp b/socket_channel.cpp
index e77c6cf..8414f51 100644
--- a/socket_channel.cpp
+++ b/socket_channel.cpp
@@ -19,12 +19,12 @@
return std::string(tmp);
}
-std::tuple<int, buffer> Channel::read()
+std::tuple<int, std::vector<uint8_t>> Channel::read()
{
int rc = 0;
int readSize = 0;
ssize_t readDataLen = 0;
- buffer outBuffer(0);
+ std::vector<uint8_t> outBuffer(0);
if (ioctl(sockfd, FIONREAD, &readSize) < 0)
{
@@ -70,7 +70,7 @@
return std::make_tuple(rc, std::move(outBuffer));
}
-int Channel::write(buffer& inBuffer)
+int Channel::write(const std::vector<uint8_t>& inBuffer)
{
int rc = 0;
auto outputPtr = inBuffer.data();