Activity log for bug #310098

Date Who What changed Old value New value Message
2008-12-20 23:03:01 Tobias C. Rittweiler bug added bug
2008-12-20 23:43:40 Nikodemus Siivola description Slime's inspector tries to use PATHNAME on any kind of FILE-STREAM object which a socket is, too. However, PATHNAME signals an (obscure) error when being tried on a socket. People expressed discomfort that sockets are not really file-streams. The way SBCL's streams are set up, all FD-STREAMS are FILE-STREAMS. This is deeply wrong, and makes things harder everyone who want to reason about pathnames associated with streams (FILE-STREAMS are valid pathname designators.) For example, Slime's inspector tries to use PATHNAME on any kind of FILE-STREAM object which a socket is, too. However, PATHNAME signals an (obscure) error when being tried on a socket. People expressed discomfort that sockets are not really file-streams. (As a stopgap measure we might return pathnames based on the FD: /dev/fd/n -- but that sucks too.)
2008-12-20 23:43:40 Nikodemus Siivola title SOCKET is a subclass of FILE-STREAM FD-STREAM is a subclass of FILE-STREAM
2008-12-20 23:43:58 Nikodemus Siivola sbcl: status New Confirmed
2008-12-20 23:43:58 Nikodemus Siivola sbcl: importance Undecided Medium
2008-12-20 23:43:58 Nikodemus Siivola sbcl: statusexplanation
2008-12-20 23:44:23 Nikodemus Siivola description The way SBCL's streams are set up, all FD-STREAMS are FILE-STREAMS. This is deeply wrong, and makes things harder everyone who want to reason about pathnames associated with streams (FILE-STREAMS are valid pathname designators.) For example, Slime's inspector tries to use PATHNAME on any kind of FILE-STREAM object which a socket is, too. However, PATHNAME signals an (obscure) error when being tried on a socket. People expressed discomfort that sockets are not really file-streams. (As a stopgap measure we might return pathnames based on the FD: /dev/fd/n -- but that sucks too.) The way SBCL's streams are set up, all FD-STREAMS are FILE-STREAMS. This is deeply wrong, and makes things harder for everyone who want to reason about pathnames associated with streams (FILE-STREAMS are valid pathname designators.) For example, Slime's inspector tries to use PATHNAME on any kind of FILE-STREAM object which a socket is, too. However, PATHNAME signals an (obscure) error when being tried on a socket. People expressed discomfort that sockets are not really file-streams. (As a stopgap measure we might return pathnames based on the FD: /dev/fd/n -- but that sucks too.)
2020-12-12 04:37:57 Douglas Katzman sbcl: status Confirmed Incomplete