| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
doesn't work any more and it doesn't seem to care anyone. Let's see if someone complains ;-)
|
|\ |
|
| | |
|
| | |
|
|\ \
| |/ |
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
| |
| | |
chars to actually follow that constraint. This requires not trusting isalnum(.) and isalpha(.) to deliver portable identical results.
|
| |
| |
| | |
own private routine TclIsBareword() that does exactly what we want.
|
| | |
|
| | |
|
| | |
|
| |
| |
| | |
condition with an assertion.
|
|\ \
| |/ |
|
| | |
|
| |
| |
| |
| | |
(code)
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
constructed for the task of script parsing. Ought to speed generation of
string representation of lists, though the effect is likely only noticeable
on long lists made up primarily of simple elements (not needing quoting).
|
| | |
|
| |
| |
| |
| | |
hex characters
|
|\ \
| |/
| | |
Rewritten guts of machinery to produce string rep of lists. [Bug 3173086]
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|\ \
| |/
| | |
Use to replace calls to isspace() and their /* INTL */ risk.
|
| |
| |
| | |
Use to replace calls to isspace() and their /* INTL */ risk.
|
|\ \
| |/ |
|
| | |
|
| |
| |
| | |
rest of Tcl source code. No ABI change. API change *should* be harmless.
|
| |
| |
| | |
the Engineering Manual.
|
|\ \
| |/
| |
| |
| |
| | |
* generic/tclCompile.c: with TclParseBackslash() where possible.
* generic/tclCompCmdsSZ.c:
* generic/tclParse.c:
* generic/tclUtil.c:
|
| |\
| | |
| | |
| | |
| | | |
* generic/tclCompile.c: with TclParseBackslash() where possible.
* generic/tclParse.c:
* generic/tclUtil.c:
|
|\ \ \
| |/ /
| | | |
* tests/parse.test: \x and \u substitutions. [Bug 3200987]
|
| |\ \
| | |/
| | | |
* tests/parse.test: \x and \u substitutions. [Bug 3200987]
|
| | |
| | |
| | | |
* tests/parse.test: \x and \u substitutions. [Bug 3200987]
|
| | | |
|
|\ \ \
| |/ /
| | | |
cause more harm than good. Purged them (except in zlib files).
|
| |\ \
| | |/
| | | |
more harm than good. Purged them.
|
| | |
| | |
| | | |
more harm than good. Purged them.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* generic/tclCkalloc.c: call stacks for memory allocation to
* generic/tclParse.c: guarantee that any size values computed
* generic/tclThreadAlloc.c: are within the domains of the routines
they get passed to. [Bugs 2557696 and 2557796].
|
| | |
| | |
| | |
| | | |
after the end of buffer, [Bug 1813528] (Joe Mistachkin).
|
| | |
| | |
| | |
| | | |
might be different, be sure to use the latter for error reporting.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
start==NULL and numBytes<0. This is coverity's bug #20
* generic/tclStringObj.c (STRING_SIZE): fix allocation for
0-length strings. This is coverity's bugs #54-5
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
EvalTokensStandard, Tcl_EvalEx, EvalEx, TclAdvanceContinuations,
TclEvalObjEx):
* generic/tclCmdMZ.c (Tcl_SwitchObjCmd, TclListLines):
* generic/tclCompCmds.c (*):
* generic/tclCompile.c (TclSetByteCodeFromAny, TclInitCompileEnv,
TclFreeCompileEnv, TclCompileScript):
* generic/tclCompile.h (CompileEnv):
* generic/tclInt.h (ContLineLoc, Interp):
* generic/tclObj.c (ThreadSpecificData, ContLineLocFree,
TclThreadFinalizeObjects, TclInitObjSubsystem,
TclContinuationsEnter, TclContinuationsEnterDerived,
TclContinuationsCopy, TclContinuationsGet, TclFreeObj):
* generic/tclParse.c (TclSubstTokens, Tcl_SubstObj):
* generic/tclProc.c (TclCreateProc):
* generic/tclVar.c (TclPtrSetVar):
* tests/info.test (info-30.0-24):
Extended parser, compiler, and execution with code and attendant
data structures tracking the positions of continuation lines which
are not visible in script Tcl_Obj*'s, to properly account for them
while counting lines for #280.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* tests/parse.test (parse-15.60): routine has no mechanism to
return the "incomplete" status of "\\\n" so calling this routine
anywhere that can be reached within a Tcl_ParseCommand() call is a
mistake. In particular, ParseComment() must not use it. [Bug 1968882].
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* 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
|