3 ms·
> TCL Could you elucidate? The biggest problem I see with people dealing with Tcl is that they carry their understanding that {} delineates scope (or somethin
by bsder 5y ago
> TCL
Could you elucidate?
The biggest problem I see with people dealing with Tcl is that they carry their understanding that {} delineates scope (or something else lexically). Of course, this is wildly untrue in Tcl as {} is simply a "quote" operator.
This stuffs people up horribly until they unlearn the idea that {} has semantic meaning.
- IshKebab 5y agoYeah sure: this works puts Hello! It should require quotes: puts "Hello!" Otherwise things get error-prone. To be fair that's probably the least of TCLs string-related issues.
- suyjuris 5y agoWhy not puts {Hello!} # or even {puts} {Hello!} ? But I do not see an advantage either way. I think you attribute to quoting issues that are caused by type-punning. The quoting rules of Tcl are simple. I mostly encountered problems when people do things like # x is not actually a list, but may appear that way if a and b are nice set x "$a $b" # Proper way: set x [list $a $b] But I fail to see how quoting could address or alleviate this.