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?

The two most sacred and defining features of TempleOS are being ring-0-only and
being identity-mapped.  Linux wants to be a secure, multi-user mainframe. 
That's the vision for Linux.  That's why it has file permissions.  The vision
for TempleOS is a modern, 64-bit Commodore 64.  The C64 was a home computer
mostly used for games.  It trained my generation how to program.  It was simple,
open and hackable.  It was not networked.  The games were not multimedia works
of art, but generated programmatically with innocent, programmer (non-artist)
quality graphics.  It was simple and unsecure.  If you don't have malware and
you don't have bugs, protection just slows things down and makes the code
complicated.