Name shadows another variable error

Peter Haworth pete at lcsql.com
Wed Nov 13 21:35:02 EST 2013


Good thought, I'll give that a try.

Jerry - what was the variable preservation setting during your test?

Pete
lcSQL Software <http://www.lcsql.com>


On Wed, Nov 13, 2013 at 6:00 PM, Monte Goulding <monte at sweattechnologies.com
> wrote:

>
> On 14/11/2013, at 12:05 PM, Peter Haworth wrote:
>
> > I think I have just found a reliable way to reproduce the above error.
> > It's not the usual circumstance it happens but it may be enough for
> RunRev
> > to track it down.  Here's what I did (by accident):
> >
> > Switch Strict Compilation mode off
> > Create a stack with  a few controls on it
> > Put some simple scripts in the card, stack and/or controls, each with a
> > local statement that names the same variable, say tVar.
> > Compile all the scripts so there are no errors in them
> > Switch Strict Compilation Mode on
> > Make a change in one of the scripts and compile it - you should get the
> > error.  If you then try to save the stack, all the scripts that name the
> > variable will be get a red dot in their script editor window tab.
> >
> > If anyone has a few minutes to verify this, I will submit a QCC report
> and
> > include a test stack.
>
> I'd love to crack that nut... it's the only thing stopping me using that
> feature... Is there any correlation between the error an turning variable
> preservation on or off?
>
> Cheers
>
> --
> M E R Goulding
> Software development services
> Bespoke application development for vertical markets
>
> mergExt - There's an external for that!
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



More information about the Use-livecode mailing list