MEMCMP(3POSIX)

📦 version 2017a, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu resolute, ubuntu stonking

💖 MEMCMP(3POSIX) — the POSIX Programmer's Manual, but make it cute 💖

okay bestie, welcome to the glow-up edition of memcmp(3POSIX) from the POSIX Programmer's Manual ✨

🌸 PROLOG 🌸

okay so first things first, real talk: this manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (so like, go check the corresponding Linux manual page for the deets on Linux behaviour, bestie), or the interface might not even be implemented on Linux at all. 💀

👑 NAME 👑

memcmp — compare bytes in memory 🧠✨

🎀 SYNOPSIS 🎀

#include <string.h>

int memcmp(const void *s1, const void *s2, size_t n);

💅 DESCRIPTION 💅

so the functionality described on this reference page is aligned with the ISO C standard. Any conflict between the requirements described here and the ISO C standard is unintentional — no cap, it's just not that deep. This volume of POSIX.1‐2017 defers to the ISO C standard. periodt. 💜

The memcmp() function shall compare the first n bytes (each interpreted as unsigned char) of the object pointed to by s1 to the first n bytes of the object pointed to by s2. like it's literally byte-by-byte comparison, it's giving "spot the difference" but for memory 🦋

The sign of a non-zero return value shall be determined by the sign of the difference between the values of the first pair of bytes (both interpreted as type unsigned char) that differ in the objects being compared. iykyk — first mismatch decides everything, the rest is just vibes 🔥

⭐ RETURN VALUE ⭐

The memcmp() function shall return an integer greater than, equal to, or less than 0, if the object pointed to by s1 is greater than, equal to, or less than the object pointed to by s2, respectively. simple as that bestie 💖

🙈 ERRORS 🙈

No errors are defined. not a single one. iconic honestly ✨

The following sections are informative.

🍓 EXAMPLES 🍓

None.

🧚 APPLICATION USAGE 🧚

None.

🌈 RATIONALE 🌈

None.

🦋 FUTURE DIRECTIONS 🦋

None.

💜 SEE ALSO 💜

  • The Base Definitions volume of POSIX.1‐2017, <string.h>

Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .

Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .

ngl the fine print ate, we love a legal moment 💅

okay that's the whole page bestie, tysm for reading 🫶 mwah 💋

— IEEE/The Open Group, 2017 🎀

📦 where this page comes from