From: "Neil Jerram" <neiljerram@googlemail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Add a `read' method for ports
Date: Mon, 9 Jun 2008 18:01:45 +0100 [thread overview]
Message-ID: <49dd78620806091001p468a7e8bt2a0d9bbb2061b61@mail.gmail.com> (raw)
In-Reply-To: <871w374p5p.fsf@gnu.org>
2008/6/8 Ludovic Courtès <ludo@gnu.org>:
> Hello Guilers!
>
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> The attached patch aims to allow an `scm_c_read ()' call for N bytes to
>> translate into a `read(2)' for N bytes in the case of unbuffered file
>> ports (such as sockets); it also allows the port's buffer to be bypassed
>> when more data is requested than can fit in the buffer.
>
> I'll commit it to both branches by the end of the week if nobody
> disagrees.
>
> Thanks,
> Ludovic.
Hi Ludovic,
Sorry for not commenting before... I've reviewed the history, and
started looking through the patches, and I'm feeling (possibly)
confused. Am I correct in thinking that the "problem" here (which you
are aiming to solve) only affects unbuffered ports?
If that's right, I'm not clear why the solution is involving so much
restructuring - can't it be done without introducing the new "read"
field?
Regards,
Neil
next prev parent reply other threads:[~2008-06-09 17:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 18:58 [PATCH] Add a `read' method for ports Ludovic Courtès
2008-06-08 21:01 ` Ludovic Courtès
2008-06-09 17:01 ` Neil Jerram [this message]
2008-06-09 20:59 ` Ludovic Courtès
2008-06-11 21:38 ` Neil Jerram
2008-06-12 0:19 ` Neil Jerram
2008-06-12 7:58 ` Ludovic Courtès
2008-06-13 0:18 ` Neil Jerram
2008-06-24 20:50 ` Ludovic Courtès
2008-07-15 19:24 ` Ludovic Courtès
2008-07-15 20:05 ` Neil Jerram
2008-07-15 22:08 ` Neil Jerram
2008-07-16 21:41 ` Ludovic Courtès
2008-09-12 20:09 ` Ludovic Courtès
2008-09-14 23:08 ` Neil Jerram
2008-09-15 1:01 ` Neil Jerram
2008-09-15 7:47 ` Ludovic Courtès
2008-09-15 7:44 ` Ludovic Courtès
2008-09-15 19:18 ` Neil Jerram
2008-09-15 19:20 ` 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=49dd78620806091001p468a7e8bt2a0d9bbb2061b61@mail.gmail.com \
--to=neiljerram@googlemail.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).