unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Nala Ginrut <nalaginrut@gmail.com>
To: Neil Jerram <neil@ossau.homelinux.net>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: Comments on ‘wip-nio’
Date: Fri, 23 Mar 2012 09:47:54 +0800	[thread overview]
Message-ID: <CAPjoZoeAkGa13g8Asmk6KJy=5eqmm=0WqGtYYFaK_DZYcmvTiQ@mail.gmail.com> (raw)
In-Reply-To: <CAPjoZoenqiheNwhzYzWd+Tohv3-Y5t2WDt7EXh8aGSfbkR-pPw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]

Besides, I think we need "write bytevector from port and return the
successful size".
Just like "write-string!/partial". Now I have to use utf8->string to
convert the bytevector to string.
Why we need such a thing? Because once we introduced Non-Block IO ,we can
not write the whole bytevector in one time. When we get EAGAIN, we must
skip the bytevector size which is successfully written then try again. So
we need a "write-bytevector!/partial" or something else.
Fortunately, we don't need such a thing for Non-Block reading since we have
call-with-bytevector-output-port which could record the size we received
conveniently.

On Fri, Mar 23, 2012 at 9:17 AM, Nala Ginrut <nalaginrut@gmail.com> wrote:

>
>
> On Fri, Mar 23, 2012 at 5:36 AM, Neil Jerram <neil@ossau.homelinux.net>wrote:
>
>>  <ludo@gnu.org>but I would guess that there are cases
>> where a module isn't already constrained like this, and still might want
>> to use a "do X in N seconds time" function.
>>
>>
>>
> I think this "do X in N seconds time" function would be useful. And it's
> better to provider a "do X in N micro-seconds" too.
>
>

[-- Attachment #2: Type: text/html, Size: 1784 bytes --]

  reply	other threads:[~2012-03-23  1:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-21 22:39 Comments on ‘wip-nio’ Ludovic Courtès
2012-03-22  2:40 ` Nala Ginrut
2012-03-22 20:40   ` Ludovic Courtès
2012-03-22 21:36     ` Neil Jerram
2012-03-23  1:17       ` Nala Ginrut
2012-03-23  1:47         ` Nala Ginrut [this message]
2012-03-23 10:01           ` Andy Wingo
2012-03-23 10:05       ` Andy Wingo
2012-03-25 20:17         ` Neil Jerram
2012-03-25 23:23           ` Andy Wingo
2012-03-25 10:46   ` Andreas Rottmann
2012-03-23  9:58 ` Andy Wingo
2012-03-27 15:50   ` 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='CAPjoZoeAkGa13g8Asmk6KJy=5eqmm=0WqGtYYFaK_DZYcmvTiQ@mail.gmail.com' \
    --to=nalaginrut@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=neil@ossau.homelinux.net \
    /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).