unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: The “binary-friendly” Latin-1
Date: Sat, 29 Jan 2011 15:29:08 +0100	[thread overview]
Message-ID: <87d3nfiy17.fsf@gnu.org> (raw)
In-Reply-To: m38vy5ffdy.fsf@unquote.localdomain

Hi Andy!

Andy Wingo <wingo@pobox.com> writes:

> On Wed 26 Jan 2011 19:31, Mike Gran <spk121@yahoo.com> 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’.




  reply	other threads:[~2011-01-29 14:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-26 18:31 The “binary-friendly” Latin-1 Mike Gran
2011-01-28 11:15 ` Andy Wingo
2011-01-29 14:29   ` Ludovic Courtès [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-01-25 14:01 Mike Gran
2011-01-25 19:58 ` Ludovic Courtès
2011-01-24 23:21 Mike Gran
2011-01-25 10:19 ` Hans Aberg
2011-01-25 13:21 ` Ludovic Courtès
2011-01-24 22:26 Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d3nfiy17.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).