Reopening a NODIRCORE stream: OTHERPROPS are getting lost

[rmkaplan]

(SETQ FOO (OPENSTREAM '{NODIRCORE} 'INPUT)
(STREAMPROP FOO 'X 'Y)
(STREAMPROP FOO 'X)
Y
(CLOSEF FOO)
(OPENSTREAM FOO 'INPUT)
(STREAMPROP FOO 'X)
NIL

The only way to attach information to persistent information to a nodircore stream is thru STREAMPROP, which sets OTHERPROPS. If another function comes in for some other purpose that requires closing and reopening, the saved information is lost.

The problem is the create-smashing in \NODIRCORE.OPENFILE. It doesn't preserve the OTHERPROPS, I propose to change that.

[masinter]

Streams are not files. You can have multiple streams on the file, and streamprop should only affect one.

Setfileinfo is the interface for changing file metadata in interlisp

[rmkaplan]

You can association arbitrary information with a DSK stream (using STREAMPROP), close the stream, reopen it, and the information is still there, attached to the stream. Not so with NODIRCORE or CORE. SETFILEINFO and only works with file-system-known properties (dates, length, and the like).

…

On Jun 4, 2022, at 5:26 PM, Larry Masinter ***@***.***> wrote: Streams are not files. You can have multiple streams on the file, and streamprop should only affect one. Setfileinfo is the interface for changing file metadata in interlisp — Reply to this email directly, view it on GitHub <#788 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJP4UHZZIROBM5FHOVTVNPXZZANCNFSM5X4E4GYQ>. You are receiving this because you authored the thread.