summaryrefslogtreecommitdiffstats
path: root/tests/execute.test
Commit message (Collapse)AuthorAgeFilesLines
* Thanks to TIP #587, convert many escapes in the testcases into the actual ↵jan.nijtmans2021-03-301-1/+1
| | | | (UTF-8) character.
* TIP 590: Recommend lowercase Package Namesjan.nijtmans2020-12-041-3/+3
|\
| * Lesser TIP #590 implementation: Only package renaming, no code changesjan.nijtmans2020-11-061-3/+3
| |\
| | * Case-sensitive package namesjan.nijtmans2020-11-031-5/+5
| |/
* | More ©-sign consolidationjan.nijtmans2020-11-231-1/+1
| |
* | Now that all Tcl source files are UTF-8 by default, we can use the ©-sign ↵jan.nijtmans2020-11-231-2/+2
|/ | | | whenever reasonable.
* Merge 8.6jan.nijtmans2020-10-301-15/+15
|\
| * Add "{}" around many "expr" commands in testcases. Also in doc/expr.njan.nijtmans2020-10-301-15/+15
| |
* | Merge 8.6jan.nijtmans2020-09-041-3/+3
|\ \ | |/
| * Let all test-cases load the "tcltest" package the same way. Depend on ↵jan.nijtmans2020-09-041-3/+3
| | | | | | | | tcltest 2.5, since we never test with earlier tcltest versions
* | Merge 8.6jan.nijtmans2020-09-011-50/+50
|\ \ | |/
| * Many more internal master/slave -> parent/child renamingsjan.nijtmans2020-09-011-52/+52
| |
* | Merge 8.6jan.nijtmans2019-09-161-1/+2
|\ \ | |/
| * execute.test: fix tests (if test started using -singleproc 1)sebres2019-09-161-1/+2
| |
* | merge 8.6sebres2019-08-271-4/+77
|\ \ | |/
| * more test casessebres2019-08-271-1/+42
| |
| * added tests covering bug [fa6bf38d07]sebres2019-08-271-4/+36
| |
* | [6bdadfba7d] Stop crash with multi-lappend and failing writesdkf2019-06-201-0/+39
|\ \ | |/
| * [6bdadfba7d] Stop crash with multi-lappend and failing writesdkf2019-06-201-0/+39
| |
* | Merge 8.7jan.nijtmans2018-09-031-8/+8
|\ \
| * | Eliminate use of wideBiggerThanInt test constraint, since it's the same as ↵jan.nijtmans2018-09-031-1/+1
|/ / | | | | | | | | | | {longIs32bit wideIs64bit}. And ... it's name is actually wrong ... Don't use int() any more in any test constraint, since it's semantics might change. We don't want the test constraints to change with it. (See: TIP# 514) Simplify implementation of wideIs64bit test constraint, just testing for 64-bit sign bit is enough.
* | merge 8.6dgp2017-10-301-3/+3
|\ \ | |/
| * Revise tests that relied on deprecated variable resolution rules.dgp2017-10-301-3/+3
| |
* | Eliminate exess spacings in many test-casesjan.nijtmans2016-03-101-3/+3
|/
* [a0ece9d6d4] The cmd field of a CmdFrame when non-NULL must point within thedgp2015-07-051-0/+9
| | | string of the corresponding codePtr->source.
* [268b23df11] When GetSrcInfoForPc() returns NULL, make sure it also setsdgp2015-06-031-0/+14
| | | | the length to a non-positive value so nothing tries to read offsets from a NULL pointer.
* No longer build tcltest.exe to run the tests,but use tclsh86.exe in ↵jan.nijtmans2012-07-291-0/+3
| | | | combination with tcltest86.dll to do that (Windows only)
* Now that we're no longer using SCM based on RCS, the RCS Keyword linesdgp2011-03-021-2/+0
|\ | | | | cause more harm than good. Purged them (except in zlib files).
| * Now that we're no longer using SCM based on RCS, the RCS Keyword lines causedgp2011-03-021-2/+0
| |\ | | | | | | more harm than good. Purged them.
| | * Now that we're no longer using SCM based on RCS, the RCS Keyword lines causedgp2011-03-011-2/+0
| | | | | | | | | more harm than good. Purged them.
| | * * generic/tclCompile.c: The value stashed in iPtr->compiledProcPtrdgp2009-06-131-1/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * generic/tclProc.c: when compiling a proc survives too long. We * tests/execute.test: only need it there long enough for the right TclInitCompileEnv() call to re-stash it into envPtr->procPtr. Once that is done, the CompileEnv controls. If we let the value of iPtr->compiledProcPtr linger, though, then any other bytecode compile operation that takes place will also have its CompileEnv initialized with it, and that's not correct. The value is meant to control the compile of the proc body only, not other compile tasks that happen along. Thanks to Carlos Tasada for discovering and reporting the problem. [Bug 2802881].
| | * * generic/tclTest.c: Backport the [testexprlongobj] testing command.dgp2008-03-071-1/+3
| | |
| | * * tests/execute.test (execute-6.8): Added tests checking thatdgp2008-03-071-2/+179
| | | | | | | | | | | | bytecode is invalidates in the right situations.
| | * * tests/appendComp.test: Backport test suite fixes of errorsdgp2004-10-281-4/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * tests/autoMkindex.test: revealed by -singleproc 1 -debug 1 * tests/exec.test: options to make test. * tests/execute.test: * tests/interp.test: * tests/io.test: * tests/namespace.test: * tests/regexpComp.test: * tests/stringComp.test: * tests/unixInit.test: * tests/winPipe.test:
| | * * generic/tclExecute.c: adding (DE)CACHE_STACK_INFO() pairs toMiguel Sofer2003-09-191-1/+9
| | | | | | | | | | | | | | | protect all calls that may cause traces on ::errorInfo or ::errorCode to corrupt the stack [Bug 804681]
| * | test name conflictdgp2009-06-131-2/+2
| | |
| * | * generic/tclCompile.c: The value stashed in iPtr->compiledProcPtrdgp2009-06-131-1/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * generic/tclProc.c: when compiling a proc survives too long. We * tests/execute.test: only need it there long enough for the right TclInitCompileEnv() call to re-stash it into envPtr->procPtr. Once that is done, the CompileEnv controls. If we let the value of iPtr->compiledProcPtr linger, though, then any other bytecode compile operation that takes place will also have its CompileEnv initialized with it, and that's not correct. The value is meant to control the compile of the proc body only, not other compile tasks that happen along. Thanks to Carlos Tasada for discovering and reporting the problem. [Bug 2802881].
| * | * generic/tclExecute.c: Stopped faulty double-logging of errors todgp2008-08-041-1/+22
| | | | | | | | | | | | | | | | | | * tests/execute.test: stack trace when a compile epoch bump triggers fallback to direct evaluation of commands in a compiled script. [Bug 2037338]
* | | * tests/execute.test (execute-11.1): [Bug 3142026]: Added test thatdkf2011-01-011-94/+124
| | | | | | | | | | | | fails (with a crash) in an unfixed memdebug build on 64-bit systems.
* | | * tests/execute.test: added execute-10.3 for [Bug 3072640]. TheMiguel Sofer2010-09-221-1/+22
| | | | | | | | | | | | test causes a mem failure.
* | | TIP #348 IMPLEMENTATION - Substituted error stackferrieux2010-04-051-3/+3
| | |
* | | Revert mistaken commitdgp2009-11-161-3/+3
| | |
* | | (forward port) Fix [Bug 2891556] and improve test to detect similar ↵ferrieux2009-11-161-3/+3
| | | | | | | | | | | | manifestations in the future. Add tcltest support for finalization.
* | | Correct failures during -singleproc 1 test suite run.dgp2009-06-241-1/+2
| | | | | | | | | | | | Correct duplicate test names.
* | | * generic/tclCompile.c: The value stashed in iPtr->compiledProcPtrdgp2009-06-131-1/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * generic/tclProc.c: when compiling a proc survives too long. We * tests/execute.test: only need it there long enough for the right TclInitCompileEnv() call to re-stash it into envPtr->procPtr. Once that is done, the CompileEnv controls. If we let the value of iPtr->compiledProcPtr linger, though, then any other bytecode compile operation that takes place will also have its CompileEnv initialized with it, and that's not correct. The value is meant to control the compile of the proc body only, not other compile tasks that happen along. Thanks to Carlos Tasada for discovering and reporting the problem. [Bug 2802881].
* | | Fix [Bug 2568434]dkf2009-02-051-38/+30
| | |
* | | * generic/tclExecute.c: Fix for [Bug 2038069] by dgp.Miguel Sofer2008-08-051-1/+16
| | | | | | | | | | | | * tests/execute.test:
* | | * generic/tclExecute.c: Stopped faulty double-logging of errors todgp2008-08-041-1/+22
|/ / | | | | | | | | | | * tests/execute.test: stack trace when a compile epoch bump triggers fallback to direct evaluation of commands in a compiled script. [Bug 2037338]
* | * tests/execute.test (execute-6.*): More tests checking thatdgp2008-03-071-17/+97
| | | | | | | | script bytecode is invalidated in the right situations.
* | * tests/execute.test (execute-6.*): More tests checking thatdgp2008-03-071-2/+81
| | | | | | | | script bytecode is invalidated in the right situations.
generated by cgit v0.12 at 2024-11-16 12:21:56 (GMT)