FD-STREAM is a subclass of FILE-STREAM

Bug #310098 reported by Tobias C. Rittweiler on 2008-12-20
4
Affects Status Importance Assigned to Milestone
SBCL
Medium
Unassigned

Bug Description

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.)

description: updated
Changed in sbcl:
importance: Undecided → Medium
status: New → Confirmed
description: updated

Besides socket based FD-STREAMS, you can also not inspect STREAM-ERROR objects (which use such streams) as the Slime inspector tries to use the pathname here too.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers