Hi! Mike Gran <[email protected]> writes:
>> From:Ludovic Courtès <[email protected]> > >> Hello! >> >> >> 1. The notion of a “binary-friendly” ISO-8859-1 encoding? It’s >> >> actually mostly gone with the iconv change, since every textual >> >> access goes through iconv. For binary accesses, the right API is >> >> (rnrs io ports) or similar. >> > >> > An equivalent question is if you care about backward compatibility of >> > legacy ports. Legacy ports returned strings and were once the only option. >> >> You mean if there’s legacy code using a port of unspecified encoding to >> read binary data, right? >> >> The iconv change doesn’t break it on GNU/Linux: > > 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. Thanks, Ludo’.
