From: SourceForge.net <no...@so...> - 2003-02-11 23:56:18
|
Feature Requests item #684982, was opened at 2003-02-11 18:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=360894&aid=684982&group_id=10894 Category: 43. Parsing and Eval Group: None Status: Open Resolution: None Priority: 5 Submitted By: Don Porter (dgp) Assigned to: miguel sofer (msofer) Summary: remove TCL_BRACKET_TERM Initial Comment: One of the flag values that can be set in interp->evalFlags is TCL_BRACKET_TERM. Setting this causes both Tcl_EvalEx() and TclSetByteCodeFromAny() to parse only to the next unquoted close-bracket when do evaluation or compilation in the interp. The only user of this power appears to be the command substitution portion of the [subst] command. It seems to me that the same effect could be achieved by appropriate calls to Tcl_ParseCommand() with its documented "nested" argument, rather than hacking around the internals of the interp structure. ---------------------------------------------------------------------- >Comment By: Don Porter (dgp) Date: 2003-02-11 19:03 Message: Logged In: YES user_id=80530 The TclPro program tclcompiler directly calls TclSetByteCodeFromAny, so it's possible it cares about this TCL_BRACKET_TERM matter. ---------------------------------------------------------------------- Comment By: Don Porter (dgp) Date: 2003-02-11 18:19 Message: Logged In: YES user_id=80530 Using the Tcl test suite as a poor man's coverage test for the Tcl source code, it appears that the code testing for TCL_BRACKET_TERM being set in TclSetByteCodeFromAny() is never active. If that's true, then TCL_BRACKET_TERM appear to exist only to configure a particular mode of operation in Tcl_EvalEx(). Would be better not to call Tcl_EvalEx() at all, but use Tcl_ParseCommand() and friends within Tcl_SubstObjCmd ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=360894&aid=684982&group_id=10894 |