Be safe_string compatible.

As per #89 request.
It might be useful to preserve backward-compatibility of exposed primitives (to allow linking with compiled code that assumes the old primitives, or not having to change client C codebases that would use those functions). Just having both names available would ensure that. On the other hand, if that's not a requirement of the project (I cannot tell), your choice to just keep the new stuff is good.