Name shadows another variable

[Peter Haworth]

Hi Mike,
My workaround is to turn off strict compilation mode, compile and turn it
back on again but that's fraught with dangerous consequences if I forget to
switch it on again.

Bottom line is, this shouldn't happen, there should be no need for any
workaround.

A recent thread talked about "paper cuts".  For me this is an open,
festering wound!

Pete
lcSQL Software <http://www.lcsql.com>
Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>


On Thu, Jun 26, 2014 at 6:08 PM, Mike Bonner <bonnmike at gmail.com> wrote:

> Not sure i'd know WHERE to do it, guess it depends on the script, but..
> could you use "delete variable..." to fix the problem without having to
> restart lc?  Of course this would probably require you to understand the
> source of the problem.  Another thing I wonder about is the variable
> preservation preference setting.  Wonder if you could pop the tick out of
> that, compile, then pop it back in.  Pain in the butt though.  There is a
> property (the preservervariables) also, that defaults to false I believe,
> but the recommendation in the dictionary is to not mess with that one.
>
>
> On Thu, Jun 26, 2014 at 5:54 PM, <dunbarx at aol.com> wrote:
>
> > Peter,
> >
> >
> > Can you tell me more about what this error is and does?
> >
> >
> > Craig
> >
> >
> >
> > -----Original Message-----
> > From: Peter Haworth <pete at lcsql.com>
> > To: How to use LiveCode <use-livecode at lists.runrev.com>
> > Sent: Thu, Jun 26, 2014 5:12 pm
> > Subject: Name shadows another variable
> >
> >
> > The above error has been flagged intermittently and incorrectly when
> > compiling a script with Strict Compilation Mode turned on for as long as
> > I've been using Livecode.
> >
> > In the last couple of days, the error has been flagged every time I
> compile
> > a script in one particular application.  I restart Livecode and all is
> OK -
> > same combination of stacks, no recompile necessary.
> >
> > As far as I know, that's the only way to get around the issue unless I
> > switch off Strict Compilation Mode which I am not willing to do.
> >
> > I know the bug has been entered at the QCC several times and I also know
> > that so far it has been impossible to provide a recipe to reproduce it. I
> > will add the stack exhibiting the problem to one of the error reports but
> > I've done that in the past and RunRev have been unable to reproduce it.
> >
> > I am practically at a standstill with development of this application
> until
> > this problem is fixed.
> >
> > It seems to me that someone at RunRev needs to take responsibility for
> > finding what causes this problem using old fashioned methods, like going
> > through the code, or reproduce it themselves.
> >
> > Pete
> > lcSQL Software <http://www.lcsql.com>
> > Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
> > SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>
> > _______________________________________________
> > 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
> >
> >
> > _______________________________________________
> > 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
> >
> _______________________________________________
> 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
>