From: SourceForge.net <no...@so...> - 2003-11-24 15:59:06
|
Bugs item #848262, was opened at 2003-11-24 09:56 Message generated for change (Settings changed) made by msofer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=848262&group_id=10894 Category: 44. Parsing and Eval Group: develop: 8.5a0 Status: Open Resolution: None >Priority: 7 Submitted By: Andreas Leitgeb (avl42) >Assigned to: Don Porter (dgp) Summary: minor bug in new {expand}-parsing Initial Comment: there are a few cases, where {expand} *without* trailer is misinterpreted to expand to nothing: in interactive tclsh8.5 shell: % list {expand} % list {expand}; % if 1 {list {expand};} % (all return the empty string, instead of the string "expand") However % if 1 {list {expand}} expand % works correctly. It looks like the code that checks the next character after the {expand} deals with too few cases. ---------------------------------------------------------------------- Comment By: Andreas Leitgeb (avl42) Date: 2003-11-24 10:07 Message: Logged In: YES user_id=830354 another failing case (also in interactive shell): % list {expand} whatever else whatever else % (since \-newline-anywhitespace should be treated as one single whitespace, the {expand}-semantics shouldn't trigger. This might be more difficult to fix than the previous cases :-( ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=848262&group_id=10894 |