| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Added tests to check that the data provided by a POST is as stated in the content-length [Bug 2715421]
|
| |
|
|
|
|
|
|
|
|
| |
This patch makes use of the 8.6 zlib support to provide for
deflate and gzip support and handles the -channel option with
compression and chunked transfer encoding. For the -handler
option we currently disable HTTP/1.1 features as we cannot
properly pass the data through to the caller.
|
|
|
|
|
| |
This bug is caused by receiving a partial HTTP response line which caused premature
switching of the state in the client package before we received the whole line.
|
|
|
|
|
|
| |
* tests/fileName.test: the wrong results for both [file dirname] and
[file tail] on "path" arguments with the PATHFLAGS != 0 intrep and
with an empty string for the "joined-on" part. [Bug 2710920]
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
* tests/tailcall.test: added tests to show that [tailcall] does
not currently always execute in constant space: interp-alias,
ns-imports and ensembles "leak" as of this commit.
|
|
|
|
| |
test was marked 'knownBug': unmark it.
|
|
|
|
|
|
|
|
|
| |
* generic/tclCmdAH.c: Tailcalls now perform properly even from
* generic/tclExecute.c: within [eval]ed scripts.
* generic/tclInt.h: More tests missing, as well as proper
exploration and testing of the interaction with "redirectors" like
interp-alias (suspect that it does not happen in constant space)
and pure-eval commands.
|
|
|
|
|
|
| |
* tests/nre.test: the failing assertion that was disabled on
2008-12-18: the assertion is correct, the fault was in the
management of expansions.
|
|
|
|
| |
* tests/tailcall.test: from within a compiled [eval] body.
|
|
|
|
|
| |
Tcl_AppendStringsToObj() no longer crashes when operating on a
pure unicode value. [Bug 2597185]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* generic/tclInt.h:
* generic/tclBasic.c:
* generic/tclExecute.c:
* generic/tclNamesp.c (Tcl_PopCallFrame): Rewritten tailcall
implementation, ::unsupported::atProcExit is (temporarily?)
gone. The new approach is much simpler, and also closer to being
correct. This commit fixes [Bug 2649975] and [Bug 2695587].
* tests/coroutine.test: Moved the tests to their own files,
* tests/tailcall.test: removed the unsupported.test. Added
* tests/unsupported.test: tests for the fixed bugs.
|
| |
|
| |
|
|
|
|
| |
brittle.
|
|
|
|
|
|
| |
* tests/fileName.test: that assumed (not "absolute" => "relative").
This is a false assumption on Windows, where "volumerelative" is
another possibility. [Bug 2571597].
|
|
|
|
|
|
|
|
|
|
|
| |
* generic/tclStringObj.c: Convert Tcl_AppendStringsToObj into
* tests/stringObj.test: a radically simpler implementation
where we just loop over calls to Tcl_AppendToObj. This fixes [Bug
2597185]. It also creates a *** POTENTIAL INCOMPATIBILITY *** in
that T_ASTO can now allocate more space than is strictly required,
like all the other Tcl_Append* routines. The incompatibility was
detected by test stringObj-6.5, which I've updated to reflect the
new behavior.
|
|
|
|
|
| |
* tests/stringObj.test: command with [teststringobj maxchars] and
update the tests.
|
|
|
|
|
|
|
| |
* generic/tclTestObj.c: accesses when we append (some part of)
* tests/stringObj.test: a Tcl_Obj to itself. Added the
appendself and appendself2 subcommands to the [teststringobj] testing
command and added tests to the test suite. [Bug 2603158]
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
* tests/interp.test: ensemble. Such conversion is not necessary
* tests/nre.test: (or even all that helpful) in the NRE-enabling
of [interp invokehidden], and it has other implications -- including
significant forkage of the 8.5 and 8.6 implementations -- that are
better off avoided if there's no gain.
|
| |
|
| |
|
|
|
|
|
|
| |
* tests/interp.test: [namespace ensemble]. Work in progress
* tests/nre.test: to NRE-enable the [interp invokehidden]
subcommand.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
which is supposed to be tested...)
|
|
|
|
|
|
| |
in certain values to construct those values with [testdstring] so
there's no lack of robustness depending on the shimmer history of
shared literals.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
in the case where [clock add] is presented with a bad switch.
* tests/clock.test (clock-65.1) Added a test case for the above
problem [Bug 2481670].
|
| |
|
| |
|
| |
|