std::memcmp(3)

πŸ“¦ version 2024.07.05, in nixpkgs unstable, opensuse-leap 16.0

πŸ’– std::memcmp(3) πŸ’–

okay bestie, welcome to the std::memcmp page from the C++ Standard Library manual. This is the byte-comparison function, and it's lowkey iconic. No cap. 🫢


✨ NAME ✨

std::memcmp - std::memcmp β€” yes bestie, the name is literally the name. It's the byte-comparing function from the C++ Standard Library manual, and it's here to tell you which buffer comes first in lexicographical order. 🫢

πŸ“œ Synopsis πŸ“œ

It's defined in the header <cstring> β€” copy that, bestie. πŸ’…

Defined in header <cstring>
int memcmp( const void* lhs, const void* rhs, std::size_t count );

So what does it actually do? It reinterprets the objects pointed to by lhs and rhs as arrays of unsigned char and compares the first count bytes of those arrays. The comparison is done lexicographically β€” like alphabetical order, but for bytes.

The sign of the result is the sign of the difference between the values of the first pair of bytes (both interpreted as unsigned char) that differ in the objects being compared. That's the whole mood. ✨

πŸŽ€ Parameters πŸŽ€

  • lhs, rhs β€” pointers to the memory buffers to compare
  • count β€” number of bytes to examine

πŸ”₯ Return value πŸ”₯

  • A negative value if the first differing byte (reinterpreted as unsigned char) in lhs is less than the corresponding byte in rhs.
  • 0 if all count bytes of lhs and rhs are equal.
  • A positive value if the first differing byte in lhs is greater than the corresponding byte in rhs.

🧠 Notes 🧠

⚠️ okay so this is important: this function reads object representations, not the object values. It's typically meaningful for only trivially-copyable objects that have no padding. Don't forget that, bestie.

For example:

  • memcmp() between two objects of type std::string or std::vector will not compare their contents. It's giving "nope, wrong layer."
  • memcmp() between two objects of type struct { char c; int n; } will compare the padding bytes whose values may differ when the values of c and n are the same. 😭
  • And even if there were no padding bytes, the int would be compared without taking into account endianness.

🌈 Example 🌈

// Run this code

#include <cstring>
#include <iostream>

void demo(const char* lhs, const char* rhs, std::size_t sz)
{
    std::cout << std::string(lhs, sz);
    const int rc = std::memcmp(lhs, rhs, sz);
    if (rc < 0)
        std::cout << " precedes ";
    else if (rc > 0)
        std::cout << " follows ";
    else
        std::cout << " compares equal to ";
    std::cout << std::string(rhs, sz) << " in lexicographical order\n";
}

int main()
{
    char a1[] = {'a', 'b', 'c'};
    char a2[sizeof a1] = {'a', 'b', 'd'};

    demo(a1, a2, sizeof a1);
    demo(a2, a1, sizeof a1);
    demo(a1, a1, sizeof a1);
}

πŸ–₯️ Output πŸ–₯️

abc precedes abd in lexicographical order
abd follows abc in lexicographical order
abc compares equal to abc in lexicographical order

πŸ‘€ See also πŸ‘€

  • strcmp β€” compares two strings (function)
  • strncmp β€” compares a certain number of characters from two strings (function)
  • C documentation for memcmp β€” the C version is right there too.

and that's the tea β˜•: source http://cppreference.com, date 2024.06.10, for std::memcmp(3). mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from