summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Merge 8.7jan.nijtmans2020-05-262-9/+17
|\
| * Merge 8.6. Add MacOS build using Clang++jan.nijtmans2020-05-262-9/+17
| |\
| | * 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
| | | |
* | | | Merge 8.7jan.nijtmans2020-05-254-3/+21
|\ \ \ \ | |/ / /
| * | | Fix compiled "string is <class>" for characters > U+FFFF. Add testcase ↵jan.nijtmans2020-05-254-3/+21
| |\ \ \ | | |/ / | | | | | | | | exposing this bug.
| | * | Fix compiled "string is <class>" for TCL_UTF_MAX=4 build, for characters > ↵jan.nijtmans2020-05-253-3/+23
| | | | | | | | | | | | | | | | U+FFFF.
* | | | Merge 8.7jan.nijtmans2020-05-202-2/+2
|\ \ \ \ | |/ / /
| * | | Adapt some comments, which are not correct for Tcl 8.7 any morejan.nijtmans2020-05-202-3/+3
| | | |
| * | | Merge-markjan.nijtmans2020-05-180-0/+0
| |\ \ \ | | |/ /
| | * | 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.
* | | | Merge 8.7jan.nijtmans2020-05-183-6/+18
|\ \ \ \ | |/ / /
| * | | If Tcl is built with external libtommath (TCL_WITH_EXTERNAL_TOMMATH is ↵jan.nijtmans2020-05-183-6/+18
| | | | | | | | | | | | | | | | | | | | defined), do the tests with the external libtommath too. Also, don't try to include <tommath.h> if BN_H_ is already defined.
* | | | Merge 8.7jan.nijtmans2020-05-149-71/+68
|\ \ \ \ | |/ / /
| * | | Merge 8.6jan.nijtmans2020-05-149-71/+68
| |\ \ \ | | |/ /
| | * | 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 8.7jan.nijtmans2020-05-133-100/+64
|\ \ \ \ \ | |/ / / /
| * | | | Sync testcases with 8.6jan.nijtmans2020-05-131-99/+45
| |\ \ \ \ | | |/ / /
| | * | | Merge-markjan.nijtmans2020-05-130-0/+0
| | |\ \ \ | | | | |/ | | | |/|
| | | * | Testcase cleanup: Sync with testcases in core-8-6-branchjan.nijtmans2020-05-131-75/+54
| | | | |
| * | | | Merge 8.6jan.nijtmans2020-05-132-1/+19
| |\ \ \ \ | | |/ / /
| | * | | 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
| | | | | | |
* | | | | | | Merge 8.7jan.nijtmans2020-05-131-1/+1
|\ \ \ \ \ \ \ | |/ / / / / /
| * | | | | | Merge 8.6jan.nijtmans2020-05-131-2/+5
| |\ \ \ \ \ \ | | |/ / / / /
| | * | | | | 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.
| | | | * | | | | Demonstration for documentation bug, and suggestion for improved wording. ↵jan.nijtmans2020-05-102-12/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | More explanation will follow in the ticket.
* | | | | | | | | Merge 8.7jan.nijtmans2020-05-122-11/+13
|\ \ \ \ \ \ \ \ \ | |/ / / / / / / /
| * | | | | | | | Little tweak to Tcl_UniCharAtIndex(): Protect against negative index, return ↵jan.nijtmans2020-05-122-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | -1 in that case.
* | | | | | | | | Merge 8.7jan.nijtmans2020-05-121-3/+16
|\ \ \ \ \ \ \ \ \ | |/ / / / / / / /
| * | | | | | | | Merge 8.6jan.nijtmans2020-05-121-3/+14
| |\ \ \ \ \ \ \ \ | | |/ / / / / / / | | | | | / / / / | | |_|_|/ / / / | |/| | | | | |
| | * | | | | | Revert implementation of Tcl_UniCharAtIndex() change done in this commit: ↵jan.nijtmans2020-05-121-1/+3
| | | |_|_|_|/ | | |/| | | | | | | | | | | | | | | | | | | | | | | | | [6596c4af31e29b5d]. Just look at the Tcl_UtfAtIndex() implementation for TCL_UTF_MAX=4: It's not the same. There are no test-cases for Tcl_UniCharAtIndex(), see [f45d0dc1a7], not really worth to write one, since the implementation of this function didn't change in 20 years.
| | * | | | | Merge 8.5jan.nijtmans2020-05-121-66/+59
| | |\ \ \ \ \ | | | |/ / / / | | | | | | / | | | |_|_|/ | | |/| | |
| | | * | | Unsplit some test-cases and renumber, for testcase which give the same ↵jan.nijtmans2020-05-121-100/+46
| | | | | | | | | | | | | | | | | | | | | | | | results for different TCL_UTF_MAX values.
* | | | | | Merge 8.7jan.nijtmans2020-05-114-47/+56
|\ \ \ \ \ \ | |/ / / / /
| * | | | | Merge 8.6jan.nijtmans2020-05-112-13/+19
| |\ \ \ \ \ | | |/ / / /
| | * | | | Fix [d402ffe76]: Win32 potential crash when using main(). Thanks to ↵jan.nijtmans2020-05-112-20/+22
| | | | | | | | | | | | | | | | | | | | | | | | Christian Werner for the Bug report and the Fix.
| * | | | | Merge 8.6jan.nijtmans2020-05-112-34/+37
| |\ \ \ \ \ | | |/ / / /
| | * | | | Tweak the Tcl_UtfPrev() implementation for TCL_UTF_MAX=4. This fixes 10 ↵jan.nijtmans2020-05-112-35/+29
| | | | | | | | | | | | | | | | | | | | | | | | testcases in 4 groups (utf-7.10, utf-7.15, utf-7.40 and utf-7.48) , where Tcl_UtfPrev() didn't jump to the beginning of the UTF-8 character, even though there was no limitation which prevented that. So, this is actually a bug-fix for the TIP #389 implementation.
* | | | | | Merge 8.7jan.nijtmans2020-05-118-12/+12
|\ \ \ \ \ \ | |/ / / / /
| * | | | | Merge 8.6jan.nijtmans2020-05-117-11/+11
| |\ \ \ \ \ | | |/ / / / | | | | / / | | |_|/ / | |/| | |
generated by cgit v0.12 at 2024-11-16 18:59:19 (GMT)