Hi Andy! Andy Wingo <[email protected]> writes:
> On Wed 26 Jan 2011 19:31, Mike Gran <[email protected]> writes: > >> recv, send, etc are clearly bytevector routines. But, if you want to keep >> backward compatibility, you should have it handle both cases. >> >> IMHO, the idea of deprecating the use of strings is the wrong one. Either >> be bold and get rid of strings for 2.0, or let them be both bytevector >> and string functions for the foreseeable future. >> >> If strings remain an option, there will have to be some mention of the >> "binary-friendly" Latin-1 encoding. ;-) > > I think recv and send should operate on bytevectors. > > I also think that if Guile is compiled with deprecated code enabled, > strings should be supported, noting that the send message should be a > latin-1 string, and that received bytes will be interpreted as latin-1 > characters. If passed a string, these functions will issue deprecation > warnings. We change the documentation to speak of bytevectors and not > strings. I concur, I’ll do this. Thanks, Ludo’.
