> From: Greg Ewing [mailto:greg at cosc.canterbury.ac.nz] > > > Is that compatible with current use? I think the current > semantics are that > > global <name> always binds name to an object with that name > at module scope. > > No, it's not quite compatible, but I don't think > it's likely to break anything much in practice. I'm almost 100% sure that it will. People tend to use the same short variable names for things, and nested functions had *better* be related ... We could not use an unadorned 'global' for such a change in semantics. It would require a new keyword. Tim Delaney
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4