On Thu Oct 17 00:42:51 2024 +0000, Elizabeth Figura wrote:
Well, this check was kind of supposed to be there as a sanity check, since we're asking the application for a buffer of the relevant size. I don't mind calling it excessive and removing it, but then we don't really need the GetMaxLength() either. Either way "capacity" is kind of a weird name for the actual content size we're going to return.
Eh, I misread a bit what's going on here. Is the application actually returning a buffer that's smaller than we request, or is it just unable to handle a request that's too large? These kind of seem like two separate changes, and I'm not sure there's a point changing the ERR to "proper" handling here (is it really proper handling?) if it doesn't per se help.