| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | | |
|
| | | | | |
|
|/ / / / |
|
| | | |
| | | |
| | | |
| | | | |
tbcload/tclcompiler packages.
|
| | | |\
| |_|_|/
|/| | | |
|
|\ \ \ \
| |/ / /
| | | |
| | | | |
needed. Trims away the part of the array that was out of sync with the opcodes.
|
| | | |
| | | |
| | | | |
needed. Trims away the part of the array that was out of sync with the opcodes.
|
| | | |
| | | |
| | | |
| | | | |
encoding bug.
|
| | | |\
| |_|_|/
|/| | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
and never use forward slashes (any more), so no need to check for that.
|
|\ \ \ \
| |/ / /
| | | |
| | | |
| | | | |
95, deprecate the use of postfix ':').
Allow lpt[5-9] just as com[5-9], and make sure that path normalization works as expected for ports > 4.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
95, deprecate the use of postfix ':').
Allow lpt[5-9] just as com[5-9], and make sure that path normalization works as expected for ports > 4.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
of chars produce in the encoding result. When the flag
TCL_ENCODING_CHAR_LIMIT is set and dstCharsPtr is not NULL, then the
initial value of *dstCharsPtr is taken as the max number of chars to produce.
The limit is imposed in a way that does not require the assistance of the
encoding's driver procs, but the flag is passed on to them in case they
can do better when they know they should. No callers updated yet.
No drivers updated yet.
One difficulty is that this necessarily imposes a pre-translation limit,
and the I/O system has a history of wanting to impose only a post-translation
limit.
|
| | | |
| | | |
| | | | |
between the dstNeeded and dstLimit values.
|
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | | |
Perhaps this is a welcome convenience for some callers, but not for Tcl's
I/O system, which has no need for that. Added a new flag value
TCL_ENCODING_NO_TERMINATE that callers can use to suppress this behavior.
This means buffers don't require so much padding, and a tiny bit of processing
is saved. Update I/O callers to use the feature.
|
|\ \ \ |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \ |
|
| |\ \ \ \ |
|
| | | | | | |
|
| |\ \ \ \ \ |
|
| | | | | | | |
|
| |_|_|/ / /
|/| | | | | |
|
| | | | | | |
|
| | | | | | | |
| \ \ \ \ \ | |
|\ \ \ \ \ \ \
| | | |_|_|/ /
| | |/| | | |
| | | | | | | |
may be fleeting, and all parts of Tcl channel ecosystem have to deal with that. New assertions and tests to keep us on track.
|
| | |\ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | | |
It may be fleeting, and all parts of Tcl channel ecosystem have to deal
with that. New assertions and tests to keep us on track.
|
| |\ \ \ \ \ \ \
| | | |/ / / / /
| | |/| | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
approach in 8.6.1 and earlier. If each level of the channel stack is to have
control over its EOF independently, we have to provide for that, even though
the Filesystem read APIs make it a big pain. Also test robustness against
varing buffer sizes.
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
passed up to become an eof of the transform before continuing on to additional
ReadRaw() from the base channel. This way we don't miss fleeting EOFs.
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
fleeting EOF in the base channel. Falls into infinite block. Regression
compared with Tcl 8.6.1.
|
| |\ \ \ \ \ \ \
| |/ / / / / / /
|/| | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | | |
If this is going to change, lets not do it by accident.
|
| | | | | | | |
| | | | | | | |
| | | | | | | | |
with the unwarranted assumption that EOF is a permanent condition.
|
| |\ \ \ \ \ \ \
|/ / / / / / / /
| | _ / / / / /
| | / / / / / |
Likely additional changes needed in the other channel transforms new in 8.6.
|
| |\ \ \ \ \ \
| | |/ / / / / |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
ability to read beyond EOF. Plenty of assert()s to keep thing from going
off track again.
|
| | | | | | | |
|
| |\ \ \ \ \ \ |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
strings back in those cases where the channel has them to offer. Also
working through all the implications of this possibility on Tcl's more
exotic channel features, like stacking.
|
|\ \ \ \ \ \ \ \
| | |_|/ / / / /
| |/| | | | | |
| | | | | | | | |
filename with invalid characters gives the right error-message. (same bug existed on UNIX too, which is now fixed)
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
filename with invalid characters gives the right error-message. (same bug existed on UNIX too, which is now fixed)
|
|\ \ \ \ \ \ \ \
| |/ / / / / / / |
|