| Ticket UUID: | 848262 | |||
| Title: | minor bug in new {expand}-parsing | |||
| Type: | Bug | Version: | obsolete: 8.5a0 | |
| Submitter: | avl42 | Created on: | 2003-11-24 12:56:33 | |
| Subsystem: | 45. Parsing and Eval | Assigned To: | dgp | |
| Priority: | 7 High | Severity: | ||
| Status: | Closed | Last Modified: | 2003-11-25 02:01:09 | |
| Resolution: | Fixed | Closed By: | dgp | |
| Closed on: | 2003-11-24 19:01:09 | |||
| Description: |
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.
| |||
| User Comments: |
dgp added on 2003-11-25 02:01:09:
File Added - 68561: 848262.patch Logged In: YES user_id=80530 Attached patch fixes bug and adds tests. Committing to HEAD... avl42 added on 2003-11-24 20:07:32: 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 :-(
| |||
Attachments:
- 848262.patch [download] added by dgp on 2003-11-25 02:01:09. [details]