[iolib-devel] iolib design issues?

[Stelian Ionescu]

On Mon, 2009-01-26 at 05:40 -0500, Matthew Mondor wrote:
> I've been trying out iolib yesterday, and unfortunately couldn't find
> any proper documentation.  I therefore started reading the source.
> I've noticed net.sockets:make-socket which appears to be the public
> interface to create a new socket.

Iolib's make-socket is largely compatible with Allegro's so you can find
documentation at
http://www.franz.com/support/documentation/current/doc/operators/socket/make-socket.htm

> Using this function without specifying :connect resulted in an :active
> socket, which I noticed the API wouldn't later let me bind.  I thus
> created a :passive one, although I noticed that this did not let me
> specify any address or port to bind to and would already bind(2) and
> listen(2).

You can specify address and port with the keywords :local-host
and :local-port. To obtain an unbound socket, use :local-host nil .

-- 
Stelian Ionescu a.k.a. fe[nl]ix
Quidquid latine dictum sit, altum videtur.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <https://mailman.common-lisp.net/pipermail/iolib-devel/attachments/20090126/9a3991a1/attachment.sig>