Ticket UUID: | 1348067 | |||
Title: | scan failures from #237 | |||
Type: | Bug | Version: | obsolete: 8.5a4 | |
Submitter: | dkf | Created on: | 2005-11-04 09:24:43 | |
Subsystem: | 23. [scan] | Assigned To: | dgp | |
Priority: | 5 Medium | Severity: | ||
Status: | Closed | Last Modified: | 2005-11-12 11:08:19 | |
Resolution: | Fixed | Closed By: | dgp | |
Closed on: | 2005-11-12 04:08:19 | |||
Description: |
The TIP#237 implementation caused tests scan-4.44 and scan-4.55 to start failing. I suspect that the tests were testing for the wrong thing before and that the current result is actually the right one. But I don't know; it's up to you to decide what to do. FYI, here's the (segment of the) test log: safe.test scan.test ==== scan-4.44 Tcl_ScanObjCmd, integer scanning, odd cases FAILED ==== Contents of test case: set x {} list [scan {+} {%i} x] $x ---- Result was: 0 {} ---- Result should have been (exact matching): -1 {} ==== scan-4.44 FAILED ==== scan-4.55 Tcl_ScanObjCmd, odd cases FAILED ==== Contents of test case: set x {} list [scan {+} %f x] $x ---- Result was: 0 {} ---- Result should have been (exact matching): -1 {} ==== scan-4.55 FAILED security.test set-old.test | |||
User Comments: |
dgp added on 2005-11-12 11:08:19:
Logged In: YES user_id=80530 committed. dgp added on 2005-11-12 11:04:43: File Added - 155965: 1348067.patch Logged In: YES user_id=80530 attached patch corrects the problem. |
Attachments:
- 1348067.patch [download] added by dgp on 2005-11-12 11:04:43. [details]