Re: The “binary-friendly” Latin-1

[Mike Gran]

> >
> > Cool.  Have you considered what you would want to do with 
> > the 'recv!' procedure?
> 
> Hmm no.  Ideas?
> 
> Perhaps the second argument could be changed to be a string, in which
> case it would issue a deprecation warning, or a bytevector.  But when
> it’s a string, it’s bound to break unless the program explicitly chooses
> a Latin-1 encoding.

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.  ;-)

Also, if bytevectors are going to be used for these things, I think
you might consider have (rnrs bytevectors) be loaded by default for 2.0.

> 
> Thanks,
> Ludo’.

Thanks,

Mike