| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |\ |
|
| | |
| | |
| | |
| | | |
once. Addation brackets in TclHasStringRep() macro
|
| | | |
|
| | |
| | |
| | |
| | | |
little less intrusive.
|
| | |
| | |
| | | |
Eliminate many unnecessary type-casts to (unsigned)
|
| |\ \
| | | |
| | | |
| | | | |
Tcl_GetIndexFromObj*() to the public interface) after positive vote from the TCT.
|
| | | |
| | | |
| | | |
| | | | |
Tcl_GetIndexFromObj*() to the public interface
|
| |\ \ \
| | | |/
| | |/| |
|
| | | | |
|
| |\ \ \
| | |/ /
| | | |
| | | | |
you doing ...!)
|
| | | |
| | | |
| | | |
| | | |
| | | | |
complains about body.chars[] usage.
(Yes, I know, this one is for Tk, but Tcl was using the same construct too ....)
|
| |\ \ \
| | |/ /
| | | /
| | |/
| |/| |
|
| | | |
|
| | |
| | |
| | | |
during deletion trace on the import
|
| |\ \
| | |/ |
|
| |\ \
| | |/ |
|
| | | |
|
| |\ \
| | |/ |
|
| | | |
|
| |\ \
| | |/ |
|
| | |
| | |
| | |
| | | |
the Master-Slave paradigm and where this makes sense.
|
| |\ \ |
|
| | |\ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add documentation for this feature to the expr man page. The keyword
"integer value" has been added to the string and expr man page.
Added TCL_PARSE_NO_UNDERSCORE flag so that the digit separator can be
disabled when need when calling TclParseNumber.
Disabled digit separator in the "scan" command when scanning integers
and floating-point numbers. This is the one place where existing code
may rely on number parsing to stop at an underscore.
Disallow underscore between the leading 0 and the radix specifiers
'x', 'o', 'b', and 'd'.
Added tests for disallowed underscore use and scan with underscores
between digits in the source string.
|
| |\ \ \ \
| | |/ / / |
|
| | |\ \ \
| | | | |/
| | | |/|
| | | | | |
exposing this bug.
|
| | | | |
| | | | |
| | | | |
| | | | | |
U+FFFF.
|
| |\ \ \ \
| | |/ / / |
|
| | |\ \ \
| | | |/ / |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
individual bytes of a string searching for '(', ')', '::' or other single bytes. It is overkill to use Tcl_UtfPrev/Tcl_UtfNext for that, since those characters can only appear as their ASCII byte, not as any other sequence.
This effectively removes the last Tcl_UtfNext() call from the core, the only ones left are in tclTest.c for test commands. So the TclUtfNext() macro doesn't make sense any more.
Remove "register" keyword from many files.
|
| |\ \ \ \ |
|
| |\ \ \ \ \ |
|
| |\ \ \ \ \ \ |
|
| |\ \ \ \ \ \ \ |
|
| |\ \ \ \ \ \ \ \
| | |/ / / / / / / |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
thourougly test yet, but seems OK at first sight.
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
used yet but that's the next step.
|
| |_|_|_|_|/ / /
|/| | | | | | | |
|
|\ \ \ \ \ \ \ \
| | |_|_|_|_|/ /
| |/| | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
in TCL_UTF_MAX>3 builds.
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
fixes all "knownBug" testcases related to tip389.
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
commit, it was not correct).
Perfectionalize TclUtfToUCS4()/TclUCS4Complete() and new (internal) function TclUCS4ToUtf(). They can help preventing bugs regarding splitting/joining surrogates. Used them in a few more places.
|
|\ \ \ \ \ \ \ \
| |/ / / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
bytes.
Tcl_UtfToUniChar() now never reads more than TCL_UTF_MAX bytes any more.
Since the UtfToUtf encoder/decoder now uses TclUtfToUCS4() it doesn't join 2 surrogates as 2 x 3-byte sequences any more. Actually, it shouldn't, because such sequences are invalid UTF-8.
Therefore, added the ucs2 constraint to testcase encoding-15.4. Let's see how TIP #573 goes, this TIP should make this change official.
Other callers of Tcl_UtfToUniChar() needs to be revised for the same problem. Most callers will need to change Tcl_UtfToUniChar() -> TclUtfToUCS4() and Tcl_UtfCharComplete() -> TclUCS4Complete(), but that's not done yet.
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
bytes.
Tcl_UtfToUniChar() now never reads more than TCL_UTF_MAX bytes any more. The UtfToUtf encoder/decoder is adapted to do attitional checks (more tricky than in Tcl 8.7, since we want compatibility with earlier 8.6 releases).
Other callers of Tcl_UtfToUniChar() needs to be revised for the same problem. Most callers will need to change Tcl_UtfToUniChar() -> TclUtfToUCS4() and Tcl_UtfCharComplete() -> TclUCS4Complete(), but that's not done yet.
|
| |/ / / / / / /
|/| | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Tcl_UtfToUniChar() are suspicious, because those cannot handle 4-byte UTF-8 sequences reliable.
So, there's more work to do, but this part can already be backported to Tcl 8.6 and see where we get.
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
failures reporting first contact with tests and code.
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Also remove some out-of-date comments.
|
|\ \ \ \ \ \ \ \ \
| |/ / / / / / / /
| | | | | | | | |
| | | | | | | | | |
testcase changed results, all of them due to the Tcl_UtfPrev() improvement. Tcl_UtfNext() is not affected: Previous implementation was based on Tcl_UtfToUniChar(), which already did this check.
|