Re: finding shadowed globals when strict compilation is on

2013-04-20 Thread Dr. Hawkins
On Sat, Apr 20, 2013 at 6:30 PM, Mark Wieder wrote: > Hmmm- > > Saturday, April 20, 2013, 6:25:38 PM, you wrote: > >> On Sat, Apr 20, 2013 at 5:55 PM, Peter Haworth wrote: >>> Maybe try the "other FInd dialog (on the Edit menu). > >> Wow. OK, so that one could find it. And the 1 instance was i

Re: finding shadowed globals when strict compilation is on

2013-04-20 Thread Mark Wieder
Hmmm- Saturday, April 20, 2013, 6:25:38 PM, you wrote: > On Sat, Apr 20, 2013 at 5:55 PM, Peter Haworth wrote: >> Maybe try the "other FInd dialog (on the Edit menu). > Wow. OK, so that one could find it. And the 1 instance was in a comment . > . . That doesn't sound right. A comment shoul

Re: finding shadowed globals when strict compilation is on

2013-04-20 Thread Dr. Hawkins
On Sat, Apr 20, 2013 at 6:06 PM, Mark Wieder wrote: > Saturday, April 20, 2013, 4:40:56 PM, you wrote: > >> Is there *any* way to find out the offending other variable when >> "local name shadows" ?? > > That's what strict compilation is supposed to do :-P Well, yeah, when the other one *exists*

Re: finding shadowed globals when strict compilation is on

2013-04-20 Thread Dr. Hawkins
On Sat, Apr 20, 2013 at 5:55 PM, Peter Haworth wrote: > Maybe try the "other FInd dialog (on the Edit menu). Wow. OK, so that one could find it. And the 1 instance was in a comment . . . > Also, are you sure a global is the problem? There's a bug > in strict compilation mode where a local va

Re: finding shadowed globals when strict compilation is on

2013-04-20 Thread Mark Wieder
Dr.- Saturday, April 20, 2013, 4:40:56 PM, you wrote: > I have a recurring problem that a variable name was apparently called > global *somewhere* in my multitude of scripts (hundreds?). > I then declare it local elsewhere, and strict compilation throws a > tizzy, blocking everything, even thoug

Re: finding shadowed globals when strict compilation is on

2013-04-20 Thread Peter Haworth
Maybe try the "other FInd dialog (on the Edit menu). Also, are you sure a global is the problem? There's a bug in strict compilation mode where a local variable in a script will sometimes be flagged as shadowing another local variable, even though it doesn't. Only way to get round it is save, qu

Re: finding shadowed globals when strict compilation is on

2013-04-20 Thread Dr. Hawkins
On Sat, Apr 20, 2013 at 4:52 PM, Colin Holgate wrote: > Does doing a Find in all open stacks help? It might--but it won't let me do that. It would *seem* that "global.*dcmd" would find any global declaration of dcmd (with regexp set, of course). But when I choose anything but current tab or all

Re: finding shadowed globals when strict compilation is on

2013-04-20 Thread Colin Holgate
Does doing a Find in all open stacks help? ___ 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

finding shadowed globals when strict compilation is on

2013-04-20 Thread Dr. Hawkins
I have a recurring problem that a variable name was apparently called global *somewhere* in my multitude of scripts (hundreds?). I then declare it local elsewhere, and strict compilation throws a tizzy, blocking everything, even though it isn't available in the local scope. Is there *any* way to