| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
intended to address possible segfault on termination of search.
|
|
|
|
| |
Tcl_ArraySearchPeek() or Tcl_ArraySearchNext() is called, only when Tcl_ArraySearchDone() is called. This avoids a crash should user code unconditionally call Tcl_ArraySearchDone() at the end of an array enumeration loop. This change does not affect array searches initiated by the Tcl script command [array startsearch].
|
|\ |
|
| |
| |
| |
| | |
variable has an active search, and modify INST_UNSET_ARRAY to fall back on the slow unset method for array elements within an array being searched. The slow unset method involves a call to DeleteSearches() which stops all active searches.
|
| |
| |
| |
| | |
more place where use of size_t can increase range.
|
| |
| |
| |
| | |
TclNewLongObj is just as good.
|
| |\
| | |
| | |
| | | |
don't set an error in the interp during LinkTraceProc(): The error is supposed to be reported as return value of this function, not the interp.
|
| | |\
| | | |
| | | |
| | | | |
don't set an error in the interp during LinkTraceProc(): The error is supposed to be reported as return value of this function, not the interp.
|
| | | |
| | | |
| | | |
| | | | |
don't set an error in the interp during LinkTraceProc(): The error is supposed to be reported as return value of this function, not the interp.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
(or 9.0) features are needed. (Differences between 8.x and 9.0 are handled by a different stub magic value)
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
function is called. Determination of immediate versus deferred deallocation is done using a new search flags field.
|
|\ \ \ \
| |/ / / |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
init.tcl.
Some simplifications in use of test restrictions.
|
| |\ \ \
| | | | |
| | | | |
| | | | | |
"ll", "I64" and "L", whatever the platform defines for long long integer. With test-cases.
|
| | | | |
| | | | |
| | | | |
| | | | | |
"ll", "I64" and "L", whatever the platform defines for long long integer. With test-cases.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
need to update documentation accordingly and to add tests demonstrating correct execution of array traces. Also need to handle early search termination due to array elements being added or removed.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
take a trip through the ArrayNext() search loop despite the fact that ArrayFirst() finds the exact element and sets the search to the end of the hash table. If exact matching is used in combination with a command that stuffs the found element back into the queue (e.g. [array anymore]), ArrayNext() will have to "find" the element again. It's the very next entry, but nevertheless it needs to confirm.
|
|\ \ \ \ \
| |/ / / / |
|
| | | | |
| | | | |
| | | | |
| | | | | |
int', but argument 2 has type 'long unsigned int'" on platforms where TCL_WIDE_INT_IS_LONG. Warning introduced by check-in [e3ba334a42] which was merged to trunk by [eac13870dc]. This fix also was made by [418b169207] which has not yet been merged to trunk.
|
|\ \ \ \ \
| |/ / / / |
|
| |/ / /
| | | |
| | | | |
interfaces usable.
|
| |\ \ \
| | | | |
| | | | | |
caching works properly in deletion callbacks (destructors!) and delete traces.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
http://paste.tclers.tk/4030
Since the epoch should bump to indicate when Tcl_FindCommand() would
produce a different result from the cached value, the bump ought to be
connected to the state change that would have that effect. This checkin
appears to be the more correct answer, and it makes the Delete path get
into agreement with the Rename path. Review would be good.
|
| |\ \ \ \
| | |/ / /
| |/| | |
| | | | | |
(now without edit-error in tcl.h, thanks Don!)
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
build on a TCL_WIDE_INT_IS_LONG platform, but leaves code in tclStringObj.c
raising compiler warnings. Suspect things still need some reconciliation
in the TCL_WIDE_INT_IS_LONG scenario.
|
| |/ / /
| | | |
| | | | |
Moved to feature branch temporarily. Breaks build.
|
| | | |
| | | |
| | | | |
the same name. This smooths migration. See obj-2.2 and tclsqlite usage.
|
| | | |
| | | |
| | | | |
as bytearrays without all this fussing about over purity.
|
| |\ \ \
| | |/ / |
|
| | |\ \
| | | |/ |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Code that to preserve bytearrays, eliminate unnecessary string rep
generation, increase efficiency, and encapsulate access to internal rep
details.
|
| | | |
| | | |
| | | |
| | | | |
Tcl_ArrayNames() treat non-array like empty array for consistency with documentation, other functions, and baseline [array names]
|
|\ \ \ \
| |/ / / |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
compile-error (non-debug) in tclDictObj.c, from previous commit
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
individual elements can be tested for. For example, [array exists arrayName *] is a higher-performance alternative to [array size arrayName] for testing if an array is non-empty since it doesn't fully enumerate the array and only checks if there is at least one matching element.
|
| | | |
| | | |
| | | |
| | | | |
to better avoid future collisions
|
| | | | |
|
| | | | |
|
| | | | |
|