string-handling

Print ovx_string_t values safely in C by using the length-aware format specifier %.*s with the string's explicit length. This prevents buffer overreads by ensuring the operation never relies on the trailing null terminator.

The best way to compare ovx_string_t values is checking length equality first, then using strncmp for exact byte matching. In C++, wrapping the data in std::string_view provides zero-copy borrowed access for efficient comparisons.

std::string_view wraps the ovx_string_t pointer and length pair for zero-copy borrowed access in C++. You must copy the data to your own storage if the string value needs to outlive the API's internal memory.

ovx_string_t requires length-aware operations because it is a (ptr, length) pair where the null terminator exists for safety but must not be relied upon. Using explicit length prevents overreads and ensures performance-sensitive text handling.

You need to copy ovx_string_t data when the string value must outlive the API's internal storage. Using std::string_view provides temporary zero-copy access, but owning the copy ensures the data remains valid after the API releases its memory.

Yes, you can use literal_to_ovx_string for converting standard string literals and is_ovx_string_empty to check for vacuous values. These helpers facilitate safe interop with APIs by correctly managing the (ptr, length) pair structure.