This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: sockets are not really ports?
- To: "C. Ray C." <crayc at 206 dot 31 dot 63 dot 15>
- Subject: Re: sockets are not really ports?
- From: Jim Blandy <jimb at red-bean dot com>
- Date: 22 Jan 2000 09:23:01 -0500
- Cc: guile at sourceware dot cygnus dot com
- References: <20000121180343.B9113@206.31.63.15>
> While implementing the server side of HTTP, I have come across three
> annoying things:
> accept blocks all threads
> select won't take a socket port
> set-current-input-port won't take a socket port
All of these ought to work fine, so I think they're all bugs.
The latter two look like type-checking bugs. Sockets certainly
support these operations at the Unix level, and Guile's buffering
shouldn't interfere at all. I suspect the type checking is rejecting
things which would work just fine.
Hopefully Gary Houston or Mikael Djurfeldt will jump in with a patch
for this. I don't really understand the internal select stuff.