summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Update TZ info to tzdata2020a.José Ignacio Marín2020-06-067-588/+277
|
* merge 8.5sebres2020-06-021-19/+16
|\
| * avoid segfault if Tcl_FreeParse, if parse structure remains uninitialized ↵sebres2020-06-021-19/+16
| | | | | | | | (parse.tokenPtr may be used uninitialized, for instance it returns from Tcl_ParseCommand etc with error before TclParseInit gets called)
* | no functional changes (closed bracket in comment, lint concerns only)sebres2020-05-292-2/+2
| |
* | Merge 8.5jan.nijtmans2020-05-261-4/+4
|\ \ | |/
| * Update from Xcode 11.4 to 11.5: Latest one should continue to work always.jan.nijtmans2020-05-201-4/+4
| |
* | Fix compiled "string is <class>" for TCL_UTF_MAX=4 build, for characters > ↵jan.nijtmans2020-05-253-3/+23
| | | | | | | | U+FFFF.
* | Tiny fix for TCL_UTF_MAX=4 build only: Since Tcl_UtfNext() verifies 4 bytes ↵jan.nijtmans2020-05-182-10/+4
| | | | | | | | for lead bytes F0-F5, Tcl_UtfCharComplete() should guarantee that those 4 bytes are available, not 3.
* | In some places, Tcl_UtfPrev()/Tcl_UtfNext() is used traversing the ↵jan.nijtmans2020-05-149-169/+163
|\ \ | | | | | | | | | | | | | | | 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.
| * | In some places, Tcl_UtfPrev()/Tcl_UtfNext() is used traversing the ↵jan.nijtmans2020-05-132-8/+7
| | | | | | | | | | | | 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.
* | | Merge-markjan.nijtmans2020-05-130-0/+0
|\ \ \ | | |/ | |/|
| * | Testcase cleanup: Sync with testcases in core-8-6-branchjan.nijtmans2020-05-131-75/+54
| | |
* | | Fix [ed29806baf]: Tcl_UtfToUniChar reads more than TCL_UTF_MAX bytesjan.nijtmans2020-05-134-165/+94
|\ \ \ | |_|/ |/| |
| * | Merge testcase cleanup. Make Tcl_UtfPrev() behave the same for any ↵jan.nijtmans2020-05-122-23/+22
| |\ \ | | | | | | | | | | | | TCL_UTF_MAX value, since we didn't figure out yet how it should behave for TCL_UTF_MAX>3.
| * | | Fix "knownBug" utf-4.11. Turns out a few other testcases where still not ↵jan.nijtmans2020-05-122-197/+59
| | | | | | | | | | | | | | | | correct, now they are. Make next/prev behavior the same for all TCL_UTF_MAX values, since the exact behavior for TCL_UTF_MAX>3 should be worked out further for Tcl 8.7 first, then everything agreed upon can be backported.
| * | | Merge 8.6. Mark testcase utf-4.11 as "knownBug": this one still doesn't give ↵jan.nijtmans2020-05-1112-178/+204
| |\ \ \ | | | | | | | | | | | | | | | the right answer. Add testcase 4.14 with similar corner-case, this one is OK.
| * | | | Change order of some testcases, matching 8.6jan.nijtmans2020-05-071-12/+12
| | | | |
* | | | | merge 8.5sebres2020-05-131-0/+18
|\ \ \ \ \ | | |_|_|/ | |/| | |
| * | | | clock.test: more tests for negative month offsets over threshold of a year ↵sebres2020-05-131-0/+18
| | | | | | | | | | | | | | | | | | | | (important for C-implementation like clock-speedup branch, see https://github.com/sebres/tclclockmod/issues/20#issuecomment-627704993)
* | | | | One Tcl_UtfPrev() -> TclUtfPrev() change. Just a little bit cheaper.jan.nijtmans2020-05-131-1/+1
| | | | |
* | | | | Fix documentation of Tcl_UtfAtIndex(), in accordance with implementation. ↵jan.nijtmans2020-05-131-1/+1
|\ \ \ \ \ | |/ / / / | | | | | | | | | | See: [81242a48c8]
| * | | | Fix documentation of Tcl_UtfAtIndex(), in accordance with implementation. ↵jan.nijtmans2020-05-131-1/+1
| |\ \ \ \ | | | | | | | | | | | | | | | | | | See: [81242a48c8]
| | * \ \ \ Change back implementation of Tcl_UtfAtIndex() to how it was. Update ↵jan.nijtmans2020-05-1210-64/+85
| | |\ \ \ \ | | | | | | | | | | | | | | | | | | | | | documentation.
| | | * \ \ \ Merge 8.6jan.nijtmans2020-05-112-13/+19
| | | |\ \ \ \ | | | | | |/ / | | | | |/| |
| | | * | | | Merge 8.6jan.nijtmans2020-05-112-34/+37
| | | |\ \ \ \
| | | * \ \ \ \ Merge 8.6jan.nijtmans2020-05-117-11/+11
| | | |\ \ \ \ \
| | * | | | | | | Demonstration for documentation bug, and suggestion for improved wording. ↵jan.nijtmans2020-05-102-12/+4
| | |/ / / / / / | | | | | | | | | | | | | | | | | | | | | | | | More explanation will follow in the ticket.
| | * | | | | | Merge 8.6jan.nijtmans2020-05-102-82/+88
| | |\ \ \ \ \ \
| | * \ \ \ \ \ \ Merge-markjan.nijtmans2020-05-100-0/+0
| | |\ \ \ \ \ \ \
| | * \ \ \ \ \ \ \ Merge 8.6jan.nijtmans2020-05-082-10/+30
| | |\ \ \ \ \ \ \ \
| | * \ \ \ \ \ \ \ \ Merge 8.6jan.nijtmans2020-05-081-2/+2
| | |\ \ \ \ \ \ \ \ \
| | * \ \ \ \ \ \ \ \ \ Merge 8.6dgp2020-05-072-33/+47
| | |\ \ \ \ \ \ \ \ \ \
| | * \ \ \ \ \ \ \ \ \ \ Merge 8.6jan.nijtmans2020-05-071-35/+29
| | |\ \ \ \ \ \ \ \ \ \ \
| | * | | | | | | | | | | | Fix [fad64a857e76f98e]: "lsearch" provides wrong errorCode with bad -stride ↵jan.nijtmans2020-05-071-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | option
| | * | | | | | | | | | | | Merge 8.6jan.nijtmans2020-05-072-34/+43
| | |\ \ \ \ \ \ \ \ \ \ \ \
| | * \ \ \ \ \ \ \ \ \ \ \ \ merge 8.6dgp2020-05-061-14/+24
| | |\ \ \ \ \ \ \ \ \ \ \ \ \
| | * \ \ \ \ \ \ \ \ \ \ \ \ \ merge 8.6dgp2020-05-061-11/+26
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \
| | * \ \ \ \ \ \ \ \ \ \ \ \ \ \ Merge-markjan.nijtmans2020-05-060-0/+0
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \
| | * \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ Merge 8.6jan.nijtmans2020-05-067-21/+22
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
| | * \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ Merge 8.6jan.nijtmans2020-05-061-8/+6
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
| | * | | | | | | | | | | | | | | | | | Remove PROTO_FLAGS here toojan.nijtmans2020-05-051-7/+2
| | | | | | | | | | | | | | | | | | | |
| | * | | | | | | | | | | | | | | | | | Merge 8.6jan.nijtmans2020-05-052-19/+19
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
| | * | | | | | | | | | | | | | | | | | | Fix Tcl_UtfPrev() such that it can never go back more than TCL_UTF_MAX ↵jan.nijtmans2020-05-052-16/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | bytes. Already done correctly on core-8-6-branch, but this was never forwarded to core-8-branch.
| | * | | | | | | | | | | | | | | | | | | Merge 8.6jan.nijtmans2020-05-053-62/+59
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
| | * \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ Merge-markjan.nijtmans2020-05-040-0/+0
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
| | * \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ Merge 8.6jan.nijtmans2020-05-041-2/+2
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
| | * \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ Merge-markjan.nijtmans2020-05-030-0/+0
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
| | * \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ Merge 8.6jan.nijtmans2020-05-022-28/+28
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
| | * \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ Improve/simplify "testutfnext" and "testutfprev" commands. Now don't need to ↵jan.nijtmans2020-05-012-428/+411
| | |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | do special things with byte arrays. You can use "testbytestring" for that. This makes it more clear which test-cases use invalid byte-sequences. Now "testutfnext" also checks whether Tcl_UtfNext() reads src[-1] and src[end], and will warn you when it does.
| | | * | | | | | | | | | | | | | | | | | | | | | | | Better structurize the UTF-8 (mainly around Tcl_UtfNext()/Tcl_UtfPrev(), but ↵jan.nijtmans2020-04-292-471/+454
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | not only those) test-cases: Selector "ucs2" is meant for Tcl 8.5: No knowledge at all about 4-byte sequences. Selector "ucs4" is meant for Tcl 8.5 or 8.7 with TCL_UTF_MAX=4 or Tcl 8.6 with TCL_UTF_MAX=6 Selector "tip389" is meant for Tcl 8.6 with TCL_UTF_MAX=4 and Tcl 8.7 with TCL_UTF_MAX=3 (of course, this is too simple: there will be testcases needing more than those 3
generated by cgit v0.12 at 2025-03-29 22:46:31 (GMT)