Anyone have any objection to adding a couple of calls to terminate and/or return null terminated strings from Parrot strings for places where an API expects a standard C string?
I'm not sure of the preferred way to handle this. It would be nice to at least try to terminate the current string buffer first if there is room in the buffer and only if that fails to do an allocate or copy. Or..... is it already there and I don't see it. -Melvin
