On 2/26/06, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote: > Alternatively, 'global' could be redefined to mean > what we're thinking of for 'outer'. Then there would > be no change in keywordage. > > There would be potential for breaking code, but I > suspect the actual amount of breakage would be > small, since there would have to be 3 scopes > involved, with something in the middle one > shadowing a global that was referenced in the > inner one with a global statement. > > Given the rarity of global statement usage to begin > with, I'd say that narrows things down to something > well within the range of acceptable breakage in 3.0. You read my mind--I made a reply similar to this on another branch of this thread just minutes ago :). I am curious to see what the community thinks about this. -Almann -- Almann T. Goo almann.goo at gmail.com
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