| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| | |
|
|\ \
| |/ |
|
| |
| |
| |
| | |
the same field, but it allows twoPtrValue.ptr2 to be used for other purposes.
|
| |
| |
| |
| |
| | |
generation where we can detect that we're not in the WrongNumArgs case.
The compiler just checks that the argument count is in the right range and
issues a standard dispatch; that's enough to do an efficient job.
|
| | |
|
| | |
|
| | |
|
|\ \ |
|
| |\ \
| | |/
| | |
| | | |
source code.
|
| | |
| | |
| | |
| | | |
source code.
|
| | |
| | |
| | |
| | |
| | | |
move up #undef, for macro which is conflicting with later stuff.
remove some unused cygwin-related code
some minor gcc warnings
|
| | | |
|
| | | |
|
|\ \ \
| |/ / |
|
| | | |
|
|/ /
| |
| |
| | |
Includes 'mapeach', 'dict map' and 'foreacha' commands, test suite (partial for 'foreacha') and man pages (except for 'foreacha').
|
|\ \
| |/
| |
| |
| | |
errors only ever happen when insufficient arguments are supplied, and
not when a path doesn't exist or a dictionary is poorly formatted (the
two cases can't be easily distinguished).
|
| |
| |
| |
| |
| | |
errors only ever happen when insufficient arguments are supplied, and
not when a path doesn't exist or a dictionary is poorly formatted (the
two cases can't be easily distinguished).
|
| | |
|
| |
| |
| |
| | |
yet certain that the added bytecode opcodes are correct; evaluation is still
needed (but the test suite does pass...)
|
|\ \
| |/
| | |
Rewritten guts of machinery to produce string rep of lists. [Bug 3173086]
|
| | |
|
| |
| |
| |
| | |
to the callers. Needs more work on comments, and testing to check for any
performance impact in either direction. Fixes reported bug.
|
|\ \ |
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The final argument had been bracePtr, the address of a boolean var, where
the caller can be told whether or not the parsed list element was enclosed
in braces. In practice, no callers really care about that. What the callers
really want to know is whether the list element value exists as a literal
substring of the string being parsed, or whether a call to
TclCopyAndCollpase() is needed to produce the list element value. Now the
final argument is changed to do what callers actually need. This is a
better fit for the calls in tclParse.c, where now a good deal of
post-processing checking for "naked backslashes" is no longer necessary.
***POTENTIAL INCOMPATIBILITY***
For any callers calling in via the internal stubs table who really do use
the final argument explicitly to check for the enclosing brace scenario.
Simply looking for the braces where they must be is the revision available
to those callers, and it will backport cleanly.
Tests for expanded literals quoting detection.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The final argument had been bracePtr, the address of a boolean var, where
the caller can be told whether or not the parsed list element was enclosed
in braces. In practice, no callers really care about that. What the
callers really want to know is whether the list element value exists as a
literal substring of the string being parsed, or whether a call to
TclCopyAndCollpase() is needed to produce the list element value. Now
the final argument is changed to do what callers actually need. This is
a better fit for the calls in tclParse.c, where now a good deal of
post-processing checking for "naked backslashes" is no longer necessary.
***POTENTIAL INCOMPATIBILITY***
For any callers calling in via the internal stubs table who really do use
the final argument explicitly to check for the enclosing brace scenario.
Simply looking for the braces where they must be is the revision available
to those callers, and it will backport cleanly.
|
| |/ |
|
| | |
|
| |
| |
| | |
rest of Tcl source code. No ABI change. API change *should* be harmless.
|
|\ \
| |/
| | |
cause more harm than good. Purged them (except in zlib files).
|
| |
| |
| | |
more harm than good. Purged them.
|
| | |
|
| | |
|
| |
| |
| |
| | |
destroyed.
|
| | |
|
| | |
|
| |
| |
| |
| | |
3009403]: Signature of Tcl_GetHashKey, Tcl_(Create|Find)HashEntry
|
| |
| |
| |
| |
| | |
* generic/tclDictObj.c (DictGetCmd): always generates an errorCode on
a failure to look up an entry.
|
| |
| |
| |
| |
| |
| |
| |
| | |
* use do { ... } while (0) in macros
* avoid shadowing one local variable with another
* use clearer 'foo.bar++;' instead of '++foo.bar;' where result not
required (i.e., semantically equivalent)
* follow Engineering Manual rules on spacing and declarations
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* generic/tclExecute.c: that they set the typePtr field to
* generic/tclIO.c: NULL so that the Tcl_Obj is not left
* generic/tclIndexObj.c: in an inconsistent state.
* generic/tclInt.h: [Bug 2857044]
* generic/tclListObj.c:
* generic/tclNamesp.c:
* generic/tclOOCall.c:
* generic/tclObj.c:
* generic/tclPathObj.c:
* generic/tclProc.c:
* generic/tclRegexp.c:
* generic/tclStringObj.c:
|
| |
| |
| |
| |
| | |
- some internal const decorations
- spacing
|
| |
| |
| |
| | |
only the objProc case was handled and not the nreProc case.
|
| |
| |
| |
| | |
etc.)
|
| | |
|
| |
| |
| |
| | |
destroyed.
|