summaryrefslogtreecommitdiffstats
path: root/generic
Commit message (Collapse)AuthorAgeFilesLines
* merge core-8-6-branchbug_67aa9a2070jan.nijtmans2017-06-021-10/+8
|\
| * Change refCount field in DictObj from int to size_t. Cherry-picked from ↵jan.nijtmans2017-06-021-10/+8
| | | | | | | | "sebres-8-6-clock-speedup-cr1" branch.
* | Fix [67aa9a207037ae67f9014b544c3db34fa732f2dc|67aa9a2070]: Security: Invalid ↵jan.nijtmans2017-06-021-3/+9
|/ | | | UTF-8 can inject unexpected characters
* fixed [a3fb3356b76ec4a853d1b86aadc08675f8bef359]: segfault by sorting of the ↵sebres2017-05-291-19/+18
| | | | large lists (firstly mistakenly introduced in [af40c6fb6940bab7]), additionally simplify done-points in Tcl_LsortObjCmd.
* Tcl_UtfToUniChar() -> TclUtfToUniChar() in various places: No change in ↵jan.nijtmans2017-05-298-58/+58
| | | | functionality, just faster if ASCII only strings are involved.
* fix build failure with TCL_MEM_DEBUG introduced by [8b717dc06a3e3d49]aspect2017-05-191-3/+3
|
* Let local variables declared from within macro's always start with ↵jan.nijtmans2017-05-092-41/+41
| | | | underscore, this fixes some gcc warnings with -Wshadow.
* [6015221f59] Segfault after overflow of [binary] field specifier numeric count.dgp2017-05-051-1/+9
|\
| * [6015221f59] Segfault after overflow of [binary] field specifier numeric count.dgp2017-05-051-1/+9
| |
* | [f9fe90d0fa] [file join] normalization. See filesystem-1.52*dgp2017-05-011-1/+11
|\ \ | |/
| * [f9fe90d0fa] [file join] normalization. See filesystem-1.52*dgp2017-05-011-1/+11
| |
* | [f34cf83dd0] An optimization was being taken in a case where it produced the ↵dgp2017-04-281-0/+7
|\ \ | |/ | | | | wrong result, failing to collapse multiple /// into /. Testing on Windows where path expectations may vary would be a good idea, but since this is just an optimization avoidance, I suspect we're ok.
| * [f34cf83dd0] An optimization was being taken in a case where it produceddgp2017-04-281-0/+7
| | | | | | | | | | the wrong result, failing to collapse multiple /// into /. Testing on Windows where path expectations may vary would be a good idea, but since this is just an optimization avoidance, I suspect we're ok.
| * [04e26c02c0] Remove useless condition that raises warnings.dgp2017-04-271-6/+2
| |
* | silence uninit variable warningsdgp2017-04-281-1/+1
| |
* | [04e26c02c0] Remove useless condition that raises warnings.dgp2017-04-271-4/+2
| |
* | [50750c735a] Fix for uninit memory handling issue in zlib transforms.bug_50750c735adkf2017-04-251-18/+16
| |
* | A better way of getting source file location information when disassembling.dkf2017-04-223-20/+54
| |
* | Don't use "0%o" format in test-cases, as it suggest's it's the normal way to ↵jan.nijtmans2017-04-141-1/+1
| | | | | | | | | | format octal numbers: it isn't. Better use "%#o". Add tests for "format" and "scan" corner-cases which weren't documented (except in TIP's) neither had tests before.
* | Revert recent commit [80252e0aed]. TIP 237 is clear that %llu is invalid.dgp2017-04-122-22/+13
| |
* | merge fix-42202ba1e5ff566esebres2017-04-121-1/+31
|\ \
| * | bug fix for [42202ba1e5ff566e0f9abb9f890e460fbc6c1c5c]: segfault by coro injectfix_42202ba1e5ff566esebres2017-04-041-1/+31
| | | | | | | | | | | | rewritten callback for ::tcl::unsupported::inject, without leave the interpreter in unusable state (inaccurate environment exchange by adding eval callback), test covered now.
* | | Fix [4b12ccb3363e81b132e8dbe12aeec596102be1a8|4b12ccb336]: format/scan %llu ↵jan.nijtmans2017-04-052-13/+22
| | | | | | | | | | | | doesn't work. Also added new test-cases showing the expected behavior.
* | | Code optimization/reduction: If TCL_WIDE_INT_IS_LONG is defined, the ↵jan.nijtmans2017-04-031-5/+12
| | | | | | | | | | | | variable useWide is always 0, so related code can be eliminated without loss of functionality.
* | | [900cb0284bc] Ensure that masking pseudo-methods used for export management ↵dkf2017-03-291-0/+1
| | | | | | | | | | | | are not introspectable directly. [cherrypick]
* | | In comments and documentation, distinguish between __int64 (a Microsoft ↵jan.nijtmans2017-03-292-3/+3
| | | | | | | | | | | | 64-bit integer type) and int64_t (C99 equivalent)
* | | Improve comment on TCL_WIDE_INT_IS_LONG, making it less misleading. jan.nijtmans2017-03-272-3/+3
|/ / | | | | In tclThreadTest.c, allow mainThreadId to be >32 bits.
* | redundant end-of-line spacingjan.nijtmans2017-03-154-16/+16
| |
* | Compile [clock clicks], [clock microseconds], [clock milliseconds] and ↵Kevin B Kenny2017-03-157-13/+174
| | | | | | | | [clock seconds].
* | Make 'clock' and 'encoding' into compilable ensembles that play with safe ↵kbk_clock_encoding_ensemblesKevin B Kenny2017-03-143-1/+113
| | | | | | | | interps
* | Make 'clock' and 'encoding' into proper compilable ensemblesKevin B Kenny2017-03-144-75/+258
| |
* | Remove "makefile.bc". Not updated for many-many years, most likely it ↵jan.nijtmans2017-03-072-2/+1
| | | | | | | | doesn't work any more and it doesn't seem to care anyone. Let's see if someone complains ;-)
* | ParseTokens failed to fully respect its numBytes argument.dgp2017-02-271-1/+4
|\ \ | |/
| * ParseTokens failed to fully respect its numBytes argument.dgp2017-02-271-1/+4
| |
* | zlib stream finalize calls deflate with no input - this case (and this caseaspect2017-02-111-2/+2
| | | | | | | | | | only) must be allowed. Fixes 2nd issue in [25842c161f], introduced by [c1aff52ef3]
* | Code cleanup (based on feedback from René Zaumseil): Only call ↵jan.nijtmans2017-02-071-118/+85
| | | | | | | | GetInvalidIntFromObj() when Tcl_GetIntFromObj() fails.
* | Fix [d0f7ba56f0e8f93b7efb5b09ebc30a824bdd577a|d0f7ba56f0]: INST_EQ ↵jan.nijtmans2017-02-011-18/+4
|\ \ | |/ | | | | first-argument NaN shortcut is too aggressive
| * Fix [d0f7ba56f0e8f93b7efb5b09ebc30a824bdd577a|d0f7ba56f0]: INST_EQ ↵jan.nijtmans2017-02-011-18/+4
| | | | | | | | first-argument NaN shortcut is too aggressive
* | Update documentation on recent changes in Tcl_LinkVar.jan.nijtmans2017-01-313-37/+27
| | | | | | | | Don't use TCL_NO_DEPRECATED for disabling tests-cases: Those were not deprecated in 8.6 yet. Minor code clean-up. No functional changes.
* | Fix [39f6304c2e90549c209cd11a7920dc9921b9f48e|39f6304c2e] follow-up: Make ↵jan.nijtmans2017-01-201-3/+4
|\ \ | |/ | | | | Tcl_LinkVar toleranto to the empty string as well
| * Fix [39f6304c2e90549c209cd11a7920dc9921b9f48e|39f6304c2e] follow-up: Make ↵jan.nijtmans2017-01-201-3/+4
| | | | | | | | Tcl_LinkVar toleranto to the empty string as well
* | Merge-mark core-8-5-branch. jan.nijtmans2017-01-111-1/+0
|\ \ | |/ | | Remove useless #undef.
* | Fix [39f6304c2e]: Tcl_LinkVar is not tolerant to minus, plus, dotjan.nijtmans2017-01-011-40/+172
|\ \ | |/
| * Little tweak: Decimal dot's should be allowed as well as first part. ↵jan.nijtmans2016-12-231-1/+1
| | | | | | | | Test-case for that as well.
| * Handle other invalid sequences, like "1234e" or "-567e+", that could be the ↵jan.nijtmans2016-12-231-5/+49
| | | | | | | | start of a valid real number.
| * Fix some comments (which were not correct any more in this branch), and ↵jan.nijtmans2016-12-221-10/+9
| | | | | | | | don't allow booleans in integer context.
| * Re-based to core-8-5-branch. jan.nijtmans2016-12-221-40/+129
| |\ | | | | | | Proposed fix for [39f6304c2e90549c209cd11a7920dc9921b9f48e|39f6304c2e], which doesn't need modifications to Double/Integer valid string representations.
| | * Merge trunk. Implement sequences like "0x", "0b" and "0o" as well. And also ↵jan.nijtmans2016-12-221-18/+62
| | |\ | | | | | | | | | | | | the "." for doubles and floats.
| | | * Make sure that Tcl_GetIntFromObj/Tcl_GetWideIntFromObj/Tcl_GetDoubleFromObj ↵jan.nijtmans2016-12-211-16/+23
| | | |\ | |_|_|/ |/| | | | | | | don't set an error in the interp during LinkTraceProc(): The error is supposed to be reported as return value of this function, not the interp.
| | * | Experimental (partial) fix for ↵jan.nijtmans2016-12-213-63/+123
| | |/ | | | | | | | | | | | | | | | [39f6304c2e90549c209cd11a7920dc9921b9f48e|39f6304c2e]: Tcl_LinkVar is not tolerant to minus, plus, dot. This handled minus and plus only, not other possible errors. Will need a TIP, because the boolean type is extended to consider '-', '+' and 'o' (necessary for being able to type 'on' or 'off') as valid booleans Dot, and integer prefixes (such as 0x) not handled yet, should be handled completely different.
generated by cgit v0.12 at 2024-11-02 04:42:36 (GMT)