What's obnoxious is the WG14 standard committee could have at any time in the last 40 years provided a standard slice and buffer type that would go a long way to discourage trash API's like this one.
I swear it's de rigueur in C that if an operation requires 5 parameters to insure the operation is error free than the function shall only take 4 parameters.
Rewriting the function with idiot mode disabled
int EVP_EncodeUpdate(EVP_ENCODE_CTX ctx, buffer_t out, const slice_t in);
How dare you give your parameters names of multiple characters!
> What's obnoxious is the WG14 standard committee could have at any time in the last 40 years
Or just use bloody C++ that solved that years ago with std::span.
Unfortunately, many C dev prefers whining about "How horribly bloated" C++ is instead of using the part that makes sense.