You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having an issue that I can't fix. When in {...} context embedded in a [...] context, variables are substituted - while they should not be.
An example:
puts"Bare:"procp1 {} { set v 111; puts"p1: $v" }
p1
puts"Braced: [proc p2 {} { set v 222; puts"p2: $v" }]"
p2
Fiz executes as:
Bare:
p1: 111
error: Unknown variable 'v' in "puts "Proc: [proc p2 {} { set v 222; puts "p2: $v"
TCLSH executes as:
Bare:
p1: 111
Braced:
p2: 222
This example might look a bit abstract, but is a simple case of another issue I'm having (adding catch support).
The "unknown variable" error is from parse_quote. I managed to add detecting {...} in there (dirty hack breaking other things, won't commit), but then I ran into another "unknown variable" error in get_word. That one, I can't seem to find a fix for.
@chanibal I don't know how difficult it would be to fix, but I can't think what to do off the top of my head, and unfortunately I haven't had a lot of time to work on these kinds of things lately,
@wernsey I understand the lack of time - don't have much myself.
This issue is not critical, but it'd be nice if you fix it at some point. This is quite an annoying incompatibility. Will add that to README.md next to the if { expr ... } thing the next time I push something.
Oh, and would you like some usage docs? Mostly command descriptions, had to do them for my use anyway and porting them shouldn't be hard, just truncate internal stuff. I don't have any syntax basics written down, but a few links to TCL docs and a list of incompatibilities should be enough.
I'm having an issue that I can't fix. When in
{...}
context embedded in a[...]
context, variables are substituted - while they should not be.An example:
Fiz executes as:
TCLSH executes as:
This example might look a bit abstract, but is a simple case of another issue I'm having (adding
catch
support).The "unknown variable" error is from
parse_quote
. I managed to add detecting{...}
in there (dirty hack breaking other things, won't commit), but then I ran into another "unknown variable" error inget_word
. That one, I can't seem to find a fix for.Any chance for a fix, @wernsey ?
The text was updated successfully, but these errors were encountered: