| Ticket UUID: | 4367201817b89224602de00b4b1cbad70180a77 | |||
| Title: | yaml relies on bad Tcl resolution behaviour revoked by TIP 278 - Tcl 9 | |||
| Type: | Bug | Version: | ||
| Submitter: | dgp | Created on: | 2017-10-31 17:02:09 | |
| Subsystem: | yaml | Assigned To: | aku | |
| Priority: | 3 Low | Severity: | Minor | |
| Status: | Open | Last Modified: | 2018-01-24 18:37:42 | |
| Resolution: | None | Closed By: | nobody | |
| Closed on: | ||||
| Description: |
Just one example:
can't read "yaml::data(finished)": no such variable
while executing
"if {!$yaml::data(finished)} {
...
yaml package is using the global namespace resolution
rules for relative varnames that TIP 278 is revoking.
| |||
| User Comments: |
aku added on 2018-01-24 18:37:42:
Commit [d50864197b] fixes all the places using `$yaml::` (and associated `info exists` commands. Unclear if that fixes all the places. Currently not running tests against 9.0a0. Actually I do, and see how the change of the major version throws all the `package require` commands and version checks out of wack. So, no usable results. And making the entirety of Tcllib friendly to 9 will be a major undertaking. Keeping ticket open, at lower priority. | |||
Home
Blog
Docs
Downloads
Tickets
Timeline
Branches
Tags
Wiki