XMSTRINGBYTECOMPARE(3)

πŸ“¦
version 2.3.8 Β· 3 versions
, in arch rolling, centos-stream 9, epel 10, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0

πŸ¦‹ XmStringByteCompare: library call edition πŸ¦‹

okay bestie, welcome to the library call for XmStringByteCompare β€” it's a compound string function that tells you the results of a byte-by-byte comparison. No cap, it's giving legacy compatibility energy.


✨ NAME ✨

XmStringByteCompare β€” A compound string function that indicates the results of a byte-by-byte comparison.


πŸ“œ SYNOPSIS πŸ“œ

#include <Xm/Xm.h>
Boolean XmStringByteCompare(
XmString s1,
XmString s2);

πŸ’– DESCRIPTION πŸ’–

⚠️ Warning: this function is obsolete and exists for compatibility with previous releases. It's not the new hotness, it's the legacy bestie.

XmStringByteCompare returns a Boolean indicating the results of a byte-by-byte comparison of two compound strings.

In general, if two compound strings are created with the same (char *) string using XmStringCreateLocalized in the same language environment, the compound strings compare as equal. If two compound strings are created with the same (char *) string and the same font list element tag set other than XmFONTLIST_DEFAULT_TAG using XmStringCreate, the strings compare as equal.

In some cases, once a compound string is put into a widget, that string is converted into an internal form to allow faster processing. Part of the conversion process strips out unnecessary or redundant information. If an application then does an XtGetValues to retrieve a compound string from a widget (specifically, Label and all of its subclasses), it is not guaranteed that the compound string returned is byte-for-byte the same as the string given to the widget originally.

  • s1 β€” Specifies a compound string to be compared with s2
  • s2 β€” Specifies a compound string to be compared with s1

🫢 RETURN 🫢

Returns True if two compound strings are identical byte-by-byte.


XmStringCreate(3) and XmStringCreateLocalized(3).


Sign-off: the footer/manual tag is XmStringByteCompare(library call), and the date slot is literally not shown on the page, but the slay is eternal πŸ’…βœ¨.