Re: [TCLCORE] Unicode in Tcl 9 - a commentary and critique

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

Op zo 29 jan. 2023 om 19:11 schreef Rolf Ade:

> It's the commit https://core.tcl-lang.org/tcl/info/515bfbe816ef7b13 from
> 2023-01-19 which makes the difference here.
>
> Prior to that the examples work (wrongly) as Ashok reported, since this
> commit this is fixed as Jan showed.
>

Another commit to be noted is this one from 2023-01-22:
    <https://core.tcl-lang.org/tcl/info/57baf6fc1f334b3d>
It fixes this ticket:
    <https://core.tcl-lang.org/tcl/info/a31caff057>

Since those 2 commits fix inconsistencies in the use of -strict,
it would be useful to have Ashok's document updated, checking
whether all inconsistencies reported regarding the use of
"-strict" are gone now. It doesn't make sense starting a
discussion on making "-strict" the default in Tcl 9.0, if
there's still a discussion on what -strict should do.

One thing is for sure: When using '-strict' (without -failindex),
an exception should be thrown for any 'illegal' bytes or
code-points. I don't want to discuss 'illegal': That's different
for every encoding (although it should be clear for utf-8/-16/-32).
Not throwing an exception when
using -strict and encountering 'illegal' bytes or code-points,
that's a bug. Please report it (unless there's already a
ticket for it), and - even better - provide a test-case and/or patch.

Do we have an agreement on what '-strict' is supposed
to do? See also:
     https://core.tcl-lang.org/tips/doc/trunk/tip/346.md

Regards,
     Jan Nijtmans