Check-in [646c56c161]

Login
Bounty program for improvements to Tcl and certain Tcl packages.
Tcl 2019 Conference, Houston/TX, US, Nov 4-8
Send your abstracts to [email protected]
or submit via the online form by Sep 9.

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:speling ficks
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 646c56c16145cb216327461c3b6829e29398478dea318ea8d602f6a178e6fccf
User & Date: dgp 2018-02-27 20:16:23
Context
2018-03-04
15:12
Vote completed on 351 and 475 check-in: 861087d681 user: kennykb tags: trunk
2018-02-27
20:16
speling ficks check-in: 646c56c161 user: dgp tags: trunk
19:48
Change 'Vote' to 'In progress' on 351 and 475 check-in: 8201d58846 user: kennykb tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to tip/502.md.

20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
	b

This is the consequence of two features of incumbent Tcl
functionality. First, passing the value "-4294967295" to
_Tcl\_GetInt\(FromObj\)_ results in a successful extraction
of the C __int__ value __1__. Generally any supported formatting
of any value between __-UINT\_MAX__ and __UINT\_MAX__ is accepted,
but trasformed into a value between __INT\_MIN__ and __INT\_MAX__.
Second, the internal routine/macro _TclGetIntForIndex\(M\)_
implements a definition of Tcl index values where any value acceptable
to _Tcl\_GetInt\(FromObj\)_ is also acceptable as an index of the
same value.  Both of these features are of questionable merit, but
the first has a fair bit of compatibility constraint attached to it
because it involves the behavior of public routines.  The second
should be more open to potential revisions.






|







20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
	b

This is the consequence of two features of incumbent Tcl
functionality. First, passing the value "-4294967295" to
_Tcl\_GetInt\(FromObj\)_ results in a successful extraction
of the C __int__ value __1__. Generally any supported formatting
of any value between __-UINT\_MAX__ and __UINT\_MAX__ is accepted,
but transformed into a value between __INT\_MIN__ and __INT\_MAX__.
Second, the internal routine/macro _TclGetIntForIndex\(M\)_
implements a definition of Tcl index values where any value acceptable
to _Tcl\_GetInt\(FromObj\)_ is also acceptable as an index of the
same value.  Both of these features are of questionable merit, but
the first has a fair bit of compatibility constraint attached to it
because it involves the behavior of public routines.  The second
should be more open to potential revisions.