| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* tests/namespace.test (namespace-17.10-12): reverted commit of
2004-05-23 and removed the tests, as it interferes with the
varname resolver and there are apps that break (AlphaTk). A fix
will have to wait for Tcl9.
* generic/tclVar.c: Caching of namespace variables disabled: no
simple way was found to avoid interfering with the resolver's idea
of variable existence. A cached varName may keep a variable's name
in the namespace's hash table, which is the resolver's criterion
for existence.
* tests/namespace.c (namespace-17.10): testing for interference
between varname caching and name resolver.
|
|
|
|
|
|
| |
* tests/unixInit.test: Unset path when done.
* tests/unload.test (unload-3.1): Verify [pkgb_sub] does not exist.
Delete interps when done.
|
|
|
|
|
|
| |
* tests/stringComp.test: stop re-use of string.test test names
* tests/regexpComp.test: stop re-use of regexp.test test names
* tests/namespace.test (namespace-46.3): Verify [p] does not exist.
|
|
|
|
|
|
| |
that it doesn't misdetect some other sort
of filesystem with a write-protected root as
being a CD-ROM drive. [Bug 918267]
|
| |
|
|
|
|
| |
* tests/io.test: Take care to use namespace variables.
|
|
|
|
|
|
|
| |
that gets cleaned up.
* tests/exec.test: Clean up the "path" array.
* tests/interp.test (interp-9.3): Initialize res, so prior values
cannot make the test fail.
|
|
|
|
|
| |
set on ::errorInfo . When left in place, that trace can cause
later tests to fail.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
properly have tclIntType used for smaller values. This corrects
TclX bug 896727 and any other 3rd party extension that created
math functions but was not yet WIDE_INT aware in them.
|
| |
|
| |
|
|
|
|
| |
referring to namespace.n for details [Bug 959180]
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
insuring that no "zombie" variables are found.
* generic/tclVar.c (TclLookupSimpleVar): comments re [Bug 736729]
(predecessor of [Bug 959052]) removed.
* tests/namespace.test: added tests 17.10-12
|
|
|
|
|
|
|
|
| |
(in tcl8.4) exteriorisations of [Bug 736729] due to the use of
tclNsVarNameType obj types. Reenabling the use of this objType
("VAR ref absolute" benchmark down to 66 ms, from 230).
Added comments in TclLookupSimpleVar explaining my current
understanding of [Bug 736729].
|
|
|
|
|
| |
tclNsVarNameType objs is still disabled, pending resolution of
[Bug 736729].
|
| |
|
|
|
|
|
| |
constraint: [Bug 231259] is closed since nov 2001, and the fix of
[Bug 729692] (INST_START_CMD) makes the test succeed.
|
|
|
|
|
| |
was effectively duplicated elsewhere (and was a hold-over from
previous versions of the page)
|
| |
|
| |
|
| |
|
|
|
|
| |
file anyway.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* generic/tclExecute.c (TclExecuteByteCode): reorganised TEBC
automatic variables, defining them in tight blocks instead of at
the function level. This has three purposes:
- it simplifies the analysis of individual instructions
- it is preliminary work to the non-recursive engine
- it allows a better register allocation by the optimiser; under
gcc3.3, this results in up to 10% runtime in some tests
|
| |
|
| |
|
|
|
|
| |
incredibly constrained.
|
| |
|
|
|
|
|
|
|
|
|
| |
where there was a sneak path from Tcl_DStringFree to
SetErrorCode(0). The result was that the error code could
be reset between a call to FindFirstFileEx and the check
of its status return, leading to a bizarre error return of
{POSIX unknown {No error}}. (Found in unplanned test -
no incident logged at SourceForge.)
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
necessary.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* tclIO.h: [SF Tcl Bug 462317], see ChangeLog entry
2001-09-26. The fix done at that time is incomplete. It
is possible to get around it if the actual read
operation is defered and not executed in the event
handler itself. Instead of tracking if we are in an
read caused by a synthesized fileevent we now track if
the OS has delivered a true event = actual data and
bypass the driver if a read finds that there is no
actual data waiting. The flag is cleared by a short or
full read.
|
| |
|