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

[Rolf A. <tcl...@po...>]

Steve Landers writes:

> On 31 Dec 2022 at 8:50 AM +0800, Brian Griffin <bri...@ea...>, wrote:
>>
>> > On Dec 30, 2022, at 3:19 PM, bch <bra...@gm...> wrote:
>> >
>> >
>> > Apologies in advance; I’ve got no ideas to contribute at the moment, and might also simply be off-base. With that out of the way -
>> > Are we getting to close to the developer (the Joe or Jane Smith
>> > writing some app in Tcl) having to know more of the implementation
>> > details of Tcl I/O than they should? I offer this as a genuine
>> > question. This question is either a reality-check, ignorant and
>> > inconsequential or somewhere in between I suppose. Looking forward
>> > to finding out.
>> > -bch
>>
>> +1
>> I have a similar concern.  It feels generally wrong to me that the
>> I/O system is critiquing the data.  The only errors I/O operations
>> should report are channel failures, not content failures.
>>
>> -Brian
>
> +1 from me.

Sorry if this sounds blant - it isn't meant so - but this is beside the
point.

Here we discuss the commmand semantics in case the programmer has asked
for getting informed about encoding errors during I/O (and not only
about channel failures).

Or should I take this statements as that you are against adding encoding
error checks to I/O for Tcl 9?

rolf