Re: [TCLCORE] More on I/O with Tcl 9

[Jan N. <jan...@gm...>]

Op di 27 dec. 2022 om 10:36 schreef apnmbx-public:

> If there is a decoding error on a read or gets, I think it is completely
> appropriate, and desirable, to immediately raise an error and not bother
> preserving or returning any data already decoded on that read. Any further
> reads should be disallowed. I see little use for an application to process
> partially read data on an ill-formed input stream.
>

In this ticket:
   <https://core.tcl-lang.org/tcl/tktview?name=b8f575aa23>
pooryorick (kind of) proposes to make a distinction between
synchronous (or non-blocking) and non-synchronous (blocking)
channels. That's not necessarily a bad idea ..... It is a
behavioural change, but it has the advantage that it doesn't
conflict with any TIP, and it maintains the expectation
mentioned numerous times that a single 'read' either
reads the complete file or throws an exception.

Currently I'm in bug-fix-only mode (sometimes NO exception
is thrown at all, which surely is a bug, tickets are already
filed). But it's worth a look, and should have been brought
into this discussion instead of being only a small comment
in a random ticket.

Regards,
      Jan Nijtmans