public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Gary Houston <ghouston@arglist.com>
To: tell@telltronics.org
Cc: guile-gtk@sourceware.cygnus.com, guile@sourceware.cygnus.com
Subject: Re: select+read on socket in gtk,guile-gtk
Date: Wed, 21 Jun 2000 15:27:00 -0000	[thread overview]
Message-ID: <20000621222755.24127.qmail@d3-s55-215-telehouse.mistral.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.21.0006192256190.29363-100000@ariel.lan.telltronics.org>

> Date: Mon, 19 Jun 2000 23:16:50 -0400 (EDT)
> From: Steve Tell <tell@telltronics.org>
> 
> Does guile-gtk provide a way to hook (file descriptors from) guile ports
> into the Gtk+ select loop?   Glib's GIOChannel's perhaps?
> I know I could fall back on gtk-idle-add, but it seems less clean.

I don't know anything about this.

> Next question then is, how do I do a non-blocking read on a guile port,
> returning as many characters as are available right now?  Is there an
> interface to the raw read(2) system call, like perl's sysread()?

There's no sysread procedure for ports in general, but recv! and 
recvfrom! can be used on socket ports.

A general sysread seems like a reasonable thing to want.  It probably
needs to be implemented as a member of the ptob structure, so that it
can work as expected for unbuffered ports.

To avoid blocking when no bytes are available at all, you'd also need
to put the port into non-blocking mode:

(define p (pipe))
(define pr (car p))
(fcntl pr F_SETFL (logior O_NONBLOCK (fcntl pr F_GETFL)))

(read-char pr) =>

standard input:7:1: In procedure read-char in expression (read-char (car p)):
standard input:7:1: Resource temporarily unavailable
ABORT: (system-error)

> What I'm ultimately trying to do is arrange for a procedure to get called
> with complete lines read from a connected TCP socket, so that information
> recieved from the server at the other end can be used to update a
> items in a guile-gtk interface.

read-line or read-delimited could probably do it, but would block.

      parent reply	other threads:[~2000-06-21 15:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-19 20:17 Steve Tell
2000-06-20 21:25 ` select+read on socket in guile,guile-gtk Steve Tell
2000-06-21 21:50   ` Steve Tell
2000-06-22  2:19     ` Mikael Djurfeldt
2000-06-21 15:27 ` Gary Houston [this message]

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

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

  git send-email \
    --in-reply-to=20000621222755.24127.qmail@d3-s55-215-telehouse.mistral.co.uk \
    --to=ghouston@arglist.com \
    --cc=guile-gtk@sourceware.cygnus.com \
    --cc=guile@sourceware.cygnus.com \
    --cc=tell@telltronics.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).