summaryrefslogtreecommitdiffstats
path: root/generic
Commit message (Collapse)AuthorAgeFilesLines
* Revised fix for memleak in [info frame]. Still pretty ugly, but not moredgp2014-07-171-1/+9
| | | so than a lot of TIP 280 machinery.
* [9969cf8ca6] Move the bailout when the ->rewind flag is set down after alldgp2014-07-171-4/+4
| | | the housekeeping matters tearing down frames (trace data) is complete.
* Backout checkin that broke test io-39.1.dgp2014-07-161-9/+1
|
* Repair improper assertion.dgp2014-07-161-1/+1
|
* Assert an equality test, not an assignmentdgp2014-07-161-1/+1
|\
| * Assert an equality test, not an assignment.dgp2014-07-161-1/+1
| |
| * Starting with Unicode 6.3, the mongolian vowel separator (U+180e) is no ↵jan.nijtmans2014-07-111-2/+2
| | | | | | | | | | | | longer a whitespace, but for Tcl it still is. "NEL/Next Line" (U+0085) should have been a Unicode whitespace, but never was in Tcl. This is corrected in Tcl 8.6, but for legacy reasons not in Tcl 8.5. Update documentation accordingly, and extend test-cases for Unicode 7 compliance.
* | [6a2d339e50] Plug memleak in INST_STR_REPLACE instruction.dgp2014-07-161-0/+2
| |
* | Modify the "gettimes" test-command to use the Tcl_Obj API. jan.nijtmans2014-07-161-7/+48
| | | | | | | | New "testbytestring" command which can be used to replace the (to-be-deprecated) "bytestring" command from tcltest and/or the "indentity" encoding. Adapt many testcases to use the "testbytestring" command.
* | [726349fab8] Stop leaking compression dictionary on zlib xform channel close.dgp2014-07-151-0/+4
| |
* | Suppress valgrind warnings about uninitialized values.dgp2014-07-111-0/+4
| |
* | [9b352768e6] Plug memleak in INST_DICT_FIRST.dgp2014-07-111-0/+8
| |
* | Stop memleak in [info frame].dgp2014-07-111-1/+9
| |
* | [3479689] Plug memory leak due to incomplete bug fix.dgp2014-07-111-12/+6
| |
* | [7368d225a6] Extend the auto-cleanup of zero ref count values passed in todgp2014-07-101-0/+3
|\ \ | |/ | | | | | | the Tcl_*SetVar*() family of routines to cover the missing case where the flags value of TCL_APPEND_VALUE is passed in alone. *** POTENTIAL INCOMAPTIBILITY***
| * [7368d225a6] Extend the auto-cleanup of zero ref count values passed indgp2014-07-101-0/+3
| | | | | | | | | | to the Tcl_*SetVar*() family of routines to cover the missing case where the flags value of TCL_APPEND_VALUE is passed in alone. *** POTENTIAL INCOMAPTIBILITY***
* | Repair buffer indexing error in Tcl_ReadRaw().dgp2014-07-101-1/+1
|\ \ | |/
| * Repair buffer indexing error in Tcl_ReadRaw() exposed by iogt-6.0 and valgrind.dgp2014-07-101-1/+1
| |
* | Don't use Tcl_GetCommandInfo when Tcl_FindCommand suffices.jan.nijtmans2014-07-091-3/+2
| |
* | The write and flush operations of reflected transforms ([chan push]) havedgp2014-07-081-2/+2
| | | | | | | | | | | | | | been converting all lower level channel errors from Tcl_WriteRaw() into EINVAL. Generally this is a perplexing discard of useful information, but worse it interferes with the EAGAIN signalling that is required to manage the BLOCKED state of a nonblocking channel. Thanks to aspect for demo scripts that pointed to the bug.
* | Update Unicode tables to Unicode 7.0jan.nijtmans2014-07-042-1063/+1194
|\ \ | |/
| * Update Unicode tables to Unicode 7.0jan.nijtmans2014-07-042-1063/+1194
| |
* | [c31ca233ca] Fix TclGetsObjBinary() so that each [gets] rediscovers whetherdgp2014-07-021-5/+4
|\ \ | |/ | | a nonblocking channel is blocked.
| * [c31ca233ca] Fix TclGetsObjBinary() so that each [gets] rediscovers whetherdgp2014-07-021-5/+4
| | | | | | a nonblocking channel is blocked.
* | Fix mismatch of Tcl_Preserve() / Tcl_Release().dgp2014-06-261-2/+1
|\ \ | |/
| * Fix mismatch of Tcl_Preserve() / Tcl_Release().dgp2014-06-261-2/+1
| |
* | Simplify / refactor Tcl_ReadRaw(). No need for CopyBuffer().dgp2014-06-241-127/+50
|\ \ | |/
| * Simplify / refactor Tcl_ReadRaw(). No need for CopyBuffer().dgp2014-06-241-127/+50
| |
* | [b47b176adf] Stop possible segfaults when variability in mutex lockaku2014-06-201-0/+16
|\ \ | |/ | | | | | | schedules cause a ForwardingResult to remain on the forwardList after it has been processed (IORChan is the origin of the code in IORTrans).
| * [b47b176adf] Stop possible segfaults when variability in mutex lockaku2014-06-201-0/+16
| | | | | | | | | | schedules cause a ForwardingResult to remain on the forwardList after it has been processed (IORChan is the origin of the code in IORTrans).
* | [b47b176adf] Stop segfault when variability in mutex lock schedules cause dgp2014-06-191-0/+6
| | | | | | | | a ForwardingResult to remain on the forwardList after it has been processed.
* | [f0f876c141] Improve consistency in error messages.dkf2014-06-174-14/+16
| |
* | [cb042d294e] Improve consistency of [dict] wrong-args error messages.dkf2014-06-151-10/+10
| |
* | Some more cleaning upbug_1b0266d8bbdkf2014-06-151-36/+44
| |
* | Make [dict replace] and [dict remove] guarantee result canonicality.dkf2014-06-151-84/+65
| |
* | Improved the error messages. dkf2014-06-073-29/+94
| | | | | | | | We do not want parsing an invalid dictionary to give errors about lists! As compensation, we get greater precision in the errorcode.
* | merge trunkdkf2014-06-061-4/+11
|\ \
| * \ When too many chars are read by ReadChars() and we trim the limits to get it ↵dgp2014-06-051-4/+11
| |\ \ | | |/ | | | | | | right on the next pass, don't forget the TCL_UTF_MAX padding demanded by Tcl_ExternalToUtf(). (Thanks for finding that, aku!) Fix the factorPtr management. It was just totaly wrong. The factor should be a ratio of the record of bytes read to the record of chars read. With those fixes, new test io-12.6 covers the "too many chars" code.
| | * When too many chars are read by ReadChars() and we trim the limits todgp2014-06-051-4/+11
| | | | | | | | | | | | | | | | | | | | | get it right on the next pass, don't forget the TCL_UTF_MAX padding demanded by Tcl_ExternalToUtf(). (Thanks for finding that, aku!) Fix the factorPtr management. It was just totaly wrong. The factor should be a ratio of the record of bytes read to the record of chars read. With those fixes, new test io-12.6 covers the "too many chars" code.
* | | merge trunkdkf2014-06-061-7/+20
|\ \ \ | |/ /
| * | Revise DiscardOutput() to account for revisions to the loop in ↵dgp2014-06-041-0/+5
| |\ \ | | |/ | | | | | | FlushChannel() which is its only caller. We need to discard the curOutPtr buffer as well, and not count on another pass through the loop to attempt to flush it (and raise the same failure again?).
| | * Revise DiscardOutput() to account for revisions to the loop in FlushChannel()dgp2014-06-041-0/+5
| | | | | | | | | | | | | | | which is its only caller. We need to discard the curOutPtr buffer as well, and not count on another pass through the loop to attempt to flush it (and raise the same failure again?).
| | * Backport I/O core fixes made known by async socket work on trunk.dgp2014-06-031-7/+15
| | |\ | | |/ | |/|
| * | These edits make all tests outside of socket-14.* pass on OSX Mavericks.dgp_async_socketdgp2014-06-031-1/+3
| | | | | | | | | | | | Several socket-14.* tests failing there, and those that pass are very slow about it. Firewall or poor networking configuration may be playing a role.
| * | These edits make the tests socket-14.11.[01] stop hanging, but also introducedgp2014-06-021-6/+12
| | | | | | | | | a whole raft of test failures. WIP.
* | | more tests, cleaning up the code a bitdkf2014-06-041-16/+13
| | |
* | | [1b0266d8bb] Working towards ensuring that all dict operations are ↵dkf2014-06-031-25/+21
|/ / | | | | | | sufficiently strict.
* | Correct the interest masks in the Tcl_CreateFileHandler() calls in ↵dgp2014-05-311-5/+12
|\ \ | | | | | | | | | PipeWatchProc(). When we are interested in both readable and writable events of a command pipeline channel, we only want the readable from the read end of the pipe, and the writable from the write end of the pipe.
| * | Correct the interest masks in the Tcl_CreateFileHandler() calls indgp2014-05-311-5/+12
| |/ | | | | | | | | PipeWatchProc(). When we are interested in both readable and writable events of a command pipeline channel, we only want the readable from the read end of the pipe, and the writable from the write end of the pipe.
* | Refinements of FlushChannel() and its callers. Notably includes removal of ↵dgp2014-05-292-111/+66
|\ \ | |/ | | | | the flag BUFFER_READY.