| Ticket UUID: | a09031e288aae03a8fcf4c0ddde342dfd645e0e0 | |||
| Title: | Performance in the general case vs accurate output of [info frame] in the presence of bs+nl | |||
| Type: | Patch | Version: | 8.6, 8.7, trunk | |
| Submitter: | leon | Created on: | 2018-12-02 12:42:38 | |
| Subsystem: | 10. Objects | Assigned To: | nobody | |
| Priority: | 5 Medium | Severity: | Minor | |
| Status: | Open | Last Modified: | 2018-12-10 20:40:06 | |
| Resolution: | None | Closed By: | nobody | |
| Closed on: | ||||
| Description: |
(text/x-fossil-wiki)
The issue has been discussed at [https://groups.google.com/forum/#!topic/comp.lang.tcl/Qd0Q11CxjgQ]. I am filing this ticket so that I can submit a patch for it. My short-term goal is to provide a quick fix that makes accurate tracking of line numbers in the presence of line continuations (backslash+newline) controllable during compile and/or run time. | |||
| User Comments: |
leon (claiming to be Added new patch) added on 2018-12-10 20:40:06:
(text/x-fossil-wiki)
The new patch contains roughly everything that should go into a quick-fix. In the previous (draft) patch I had reported an issue that the experimental change didn't crash where I wouldn't be surprised if it did. The investigation showed that the old code written related to the handling of line continuations contained all required NULL-pointer checks. In particular all calls of the function TclContinuationsEnterDerived are protected with checks that its last argument is non-NULL. Therefore in this version I just added build- and run-time control over the functionality that was unconditionally disabled by the previous patch. | |||
Home
Timeline
Branches
Tags
Tickets
Download
Wiki