unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Daniel Hartwig <mandyke@gmail.com>
To: Nala Ginrut <nalaginrut@gmail.com>, guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] read-response-body should return received data when any break happens
Date: Fri, 16 Mar 2012 11:24:57 +0800	[thread overview]
Message-ID: <CAN3veRdbiydWqVWFJX5gz9tvT0sUk5x+k5g61iaiJW0b+m+zVA@mail.gmail.com> (raw)
In-Reply-To: <CAPjoZocP9k_+uh5q9u_w7YQ1O3D=7BKL0M-BTnLaR75ZPW9K4g@mail.gmail.com>

On 16 March 2012 10:23, Nala Ginrut <nalaginrut@gmail.com> wrote:
> @Daniel: I realized that seems make "get-bytevector-n" return the received
> data rather than read-response-body is better. But I'm afraid that it'll
> conflict with the definition "get-bytevector-n". Say, we ask for n bytes,
> but it returned m bytes less than n. So the user maybe get confused with the
> name "get-bytevector-n".
>

The definition of get-bytevector-n states what happens when fewer than
'count' bytes are read. Also, get-bytevector-n! says it returns the
number of bytes read as an integer.  So... I don't see where the
conflict is?



  reply	other threads:[~2012-03-16  3:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-11 15:35 [PATCH] read-response-body should return received data when any break happens Nala Ginrut
2012-03-15 16:09 ` Daniel Hartwig
2012-03-15 18:37   ` Ian Price
2012-03-15 18:48     ` Daniel Hartwig
2012-03-16  2:23       ` Nala Ginrut
2012-03-16  3:24         ` Daniel Hartwig [this message]
2012-03-16  3:31         ` Nala Ginrut
2012-03-15 18:31 ` Ian Price

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=CAN3veRdbiydWqVWFJX5gz9tvT0sUk5x+k5g61iaiJW0b+m+zVA@mail.gmail.com \
    --to=mandyke@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=nalaginrut@gmail.com \
    /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).