Ic. Well if it worked that way, then there would be no point in declaring it's scope (forgive me if that is not the right term) to begin with, as all variables would only have one "scope" that being global. Maybe I'm not getting it.
Bob On Jul 7, 2011, at 5:52 PM, Mark Wieder wrote: > Bob- > > Thursday, July 7, 2011, 9:11:51 AM, you wrote: > >> I don't think it's a bug IMHO. How can a variable in the same >> script have 2 scopes? How would the app know which you were talking >> about when you used it? > > Well, see, that's where I think it's a bug. If there's a global xyzzy > in memory I don't think the compiler should let me use a local xyzzy, > no matter whether I declare the global in the script or not. If you > have a global variable in a script and you try to redeclare it as a > local variable the compiler won't let you do that. > > Using the same name for both is a bad idea in the first place, whether > or not you can get away with it. > > -- > -Mark Wieder > mwie...@ahsoftware.net > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
