memcpy in string.h

$ man memcpy
MEMCPY(3)                          Linux Programmer's Manual                         MEMCPY(3)



NAME
       memcpy - copy memory area

SYNOPSIS
       #include <string.h>

Why the fuck is memcpy in string.h? It is not exclusively for dealing with strings, shouldn't it be with malloc, exit & co. in stdlib.h?

I'm aware that this is because of the ISO specification, and that it is probably like this for historical reasons, but what are those historical reasons?

>>21,22
WAT FUCKIN SHITTY C LIBRARIES R U CUNTS LOOKIN' AT?

BACK IN MY DAY WE KEPT memory.h SEPARATE FROM string.h 'CAUSE BACK IN DOSE DAYS PROGRAMMERS WEREN'T GIRLY RETOIDS WHO WERE SCARED OF POOP. WE DID SHIT. WE DIDN'T SIT AROUND ALL DAY LIKE A BUNCH OF GIRLS, DRINKING TEA, AND WRITING FANCY SCHMANCY MATH BOY STANDARDS LIKE DA ONES YA SEE TODAY.