> No. Pelr *must* support binary data *and* strings. At the moment, this > happens to be byte strings and utf8-strings, but this does not need to stay > that way. In that currently a scalar can be a number or a string, and the representation is hidden from the user (nearly all the time except in cases like syscall()) it might be sensible to have an interface like SvIOK, SvPOK such that "binary" and "string" were two distinct (convertible) types which might happen to be implemented inside the SV * as a buffer pointer and a flag? And that C and XS code uses one or other set of macros depending on whether it wants binary (octet) data, or string data? Except how on earth does one do this before perl6? [in that you have to make the decision as to whether the current macro names give you binary or string and thereby break something] Nicholas ClarkThread Previous | Thread Next