I use the function below "writeFileBytes" to write the contents of a std::vector<unsigned char>
to a file. I want to use the type "unsigned char" to save the file (note that is made a cast for "char"). The reason for that question is because "unsigned char" has compatibility with any byte ("00000000" bits, for example). When we use "char" we have some problems with the manipulation of certain "invalid" chars.
See this topic What is the most suitable type of vector to keep the bytes of a file? for more information about the issues with "00000000" bits (1 byte).
void writeFileBytes(const char* filename, std::vector<unsigned char>& fileBytes){
std::ofstream file(filename, std::ios::out|std::ios::binary);
file.write(fileBytes.size() ? (char*)&fileBytes[0] : 0,
std::streamsize(fileBytes.size()));
}
writeFileBytes("xz.bin", fileBytesOutput);
Is there a way to use the type "unsigned char" natively to write to a file?
This concern really make sense?
UPDATE I:
Is there a way to use the type "unsigned char" natively to write to a file? -> YES!
Following the krzaq's guidelines!
void writeFileBytes(const char* filename, std::vector<unsigned char>& fileBytes){
std::ofstream file(filename, std::ios::out|std::ios::binary);
std::copy(fileBytes.cbegin(), fileBytes.cend(),
std::ostream_iterator<unsigned char>(file));
}
UPDATE II:
This concern really make sense? -> In some ways, YES!
As I comment below...
"...'unsigned char' seems to have a 'higher level of compatibility' (include '00000000' bits). When we try to convert these 8 bits ('00000000' bits) to 'char' we have no value unlike 'unsigned char'. With 'unsigned char' we have an invalid/unrecognized 'char' value, but we have..."
See this topic What is the most suitable type of vector to keep the bytes of a file? for more information!