Matthew D. Swank writes:
> Thomas F. Burdick <tburdick <at> gmail.com> writes:
> > On Fri, Jun 27, 2008 at 5:37 AM, Matthew D. Swank
> > <akopa.gmane.poster <at> gmail.com> wrote:
> > >
> > > There is a problem in trying to use the abstract namespace for AF_LOCAL.
> > > Address in the abstract namespace are _not_ C strings.
> > >
> > > Would it be possible to ... support a subtype of LOCAL-SOCKET
> > It should be pretty simple to support byte arrays as specifying
> > abstract namespace addresses. That sounds like the most reasonable
> > interface, too.
> It does seems kind of low level to be reduced to using byte array in this
> particular instance, especially when it's "just" a special string conversion.
There are alternatives:
* have a subclass of LOCAL-SOCKET for sockets whose addresses are in the
* add an :ABSTRACTP keyword to the MAKE-SOCKADDR-FOR method for
LOCAL-SOCKET, and have the method prepend a null byte in the
However, the unix(7) page on Linux seems to imply that addresses in the
abstract namespace can be any arbitrary sequence of octets of length
UNIX_PATH_MAX-1. If that's so, not all addresses in the abstract
namespace will be representable as Lisp strings in an SBCL with
:SB-UNICODE. So it might still be worthwhile to allow the user to
supply arrays of octets as the "filename" in any case.