| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ \ \ \ \ \ \ \
| |_|/ / / / / / /
|/| | / / / / / /
| | |/ / / / / /
| |/| | | | | | |
|
| | | | | | | | |
|
| |/ / / / / /
|/| | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Test suite very unhappy with this. Shoving into
a mistake branch until that's sorted.
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
obvious that the value is octal.
dgp: Isn't the better way to make it obvious the values
are octal to use the explicit octal notation?
For example, [testchmod 0o777 $path] ?
Really seems like a bad idea to me to introduce *more*
incompatibilities for the planned conversion for
having the value 0777 stop meaning 255 and start
meaning 777 in Tcl 9.
Answer (Jan). You guessed exactly what's my follow-up plan. This was an intermediate step which keeps all test-cases running.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
by my editor in [79ace7b793] - to valid UTF-8: This way my editor will not mangle them again, and fossil will show in the UI which characters are supposed to be there.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
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.
|
|\ \ \ \ \ \ \
| |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | | |
longer a whitespace, but for Tcl it still is.
Update documentation accordingly, and extend test-cases for Unicode 7 compliance.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
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.
|
| | | | | | | |
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| |/ / / / / / |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | | |
tests in the suite.
|
|\ \ \ \ \ \ \
| |/ / / / / /
| | | | | | /
| |_|_|_|_|/
|/| | | | | |
a nonblocking channel is blocked.
|
| | | | | |
| | | | | |
| | | | | | |
a nonblocking channel is blocked.
|
| | | | | | |
|
|\ \ \ \ \ \
| |/ / / / / |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
We do not want parsing an invalid dictionary to give errors about lists!
As compensation, we get greater precision in the errorcode.
|
|\ \ \ \ \ \ |
|
| |\ \ \ \ \ \
| | |/ / / / / |
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | |/ / / / /
| | | | | | |
| | | | | | | |
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.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
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.
|
|\ \ \ \ \ \ \
| |/ / / / / / |
|
| | | | | | |
| | | | | | |
| | | | | | | |
a whole raft of test failures. WIP.
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| |/ / / / / / |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
but don't resolve localhost to ::1 (and vice versa for IPv4 and 127.0.0.1).
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | | |
sufficiently strict.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | | |
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.
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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.
|
|\ \ \ \ \ \
| |/ / / / /
| | | | | |
| | | | | | |
the flag BUFFER_READY.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
the OS networking machinery gets backed up and blocks.
Added several TODO comments on potential simplifications.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | | |
| \ \ \ \ \ | |
|\ \ \ \ \ \ \
| | |/ / / / /
| | | | | | |
| | | | | | | |
particular not allowing them to leak between multiple layers of a stacked channel. Much common code refactored into ChanRead().
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
What happened is that now that EOF flags no loger leak acros channel
stack layers, an EOF in the bottom channel isn't detected in the top one
until the ChanRead call at the top level actually returns 0 bytes. This
causes one more query/ma
|
| | |\ \ \ \ \ |
|
| | |\ \ \ \ \ \ |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
longer leaking across channel stacks.
|