Okay, clearly we're not going to reach any kind of consensus on this. We seem to be pretty thoroughly split between those who want to keep it as toStringz and those who want to rename it to toCString. Interestingly enough, _no one_ seems to want to go with just camelcasing it to toStringZ. But regardless, without anything close to a consensus on this, it wouldn't make any sense to change the function's name and break all of the code that doing that would break. So, it's going to stay toStringz.
I'll look at renaming toUTF16z to toWStringz to match toStringz (as was suggested by a couple of people in this thread), but I think that I'll wait to do that in a future pull request. As it is, both of those functions should arguably be augmented to take multiple string types, rather than just string or char[], which will take additional work, and that pull request is already large enough as it is. So, that can wait. But regardless, toStringz is staying toStringz. - Jonathan M Davis
