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

[<apn...@ya...>]

I'm not clear on why the developer would need to know the implementation
details. They do need to be aware of the encoding for the input stream and
decide on a strategy for handling streams that do not conform to the
encoding. That has nothing to do with the implementation detail.

With regards to the principle of least astonishment, while that was the norm
in protocol implementations a while ago, the resulting security related bugs
have changed the thinking in that regard. The Unicode Tech report #36 has
more on the issues of "loose" behavior on input.

/Ashok

-----Original Message-----
From: Peter Da Silva <pet...@fl...> 

On 2022-12-30, at 17:19, bch <bra...@gm...> wrote:
> 
> 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.

Isn't that kind of implied by the decision to use -strictencoding 1?

Or is that going to be the default? I would think that violates the
principle of least astonishment *and* the robustness principle (be
conservative in what you generate, be liberal in what you expect)?

_______________________________________________
Tcl-Core mailing list
Tcl...@li...
https://lists.sourceforge.net/lists/listinfo/tcl-core