enh <enh@google.com> writes:

> the crazy part is that it was an _empty_ file until i made it just
> #include <string.h>:
> https://android-review.googlesource.com/c/platform/bionic/+/52171
>
> i can't explain that (it was originally checked in as an empty file,
> so the history is no help).
>
> i _can_ explain why i made it match glibc rather than just deleting it
> though: i didn't want to break existing code that was [harmlessly]
> including an empty file, and i wanted to increase the amount of the
> code from other libcs that would "just work". (and note that ios/macos
> have a <memory.h> that's just a #include <string.h> too.)

I think this partially confirms my suspicion earlier, that the only
reason anyone ever included <memory.h> is because on some system stuff
they wanted was not in <string.h> (but was only in the latter on some).
So the former tends to be included only when the latter is also, to
cover both cases.

I'd confirm definitely by getting the list of files from Debian
codesearch that include one and the other and comparing it, but I wasn't
able to figure out how to do that.
-- 
Arsen Arsenović