"LiveCode Infinity": lexically-scoped variables and bytecode blocks

Ralph DiMola rdimola at evergreeninfo.net
Tue Jun 7 17:43:55 CEST 2016


What about an enable "lexically-scoped variables in LCS" option check box in
preferences or maybe an option in the stack so "lexically-scoped variables
in LCS" is scoped by stack? The latter is probably the better option so
existing library stacks won't be affected but a new main stack can have
"lexically-scoped variables in LCS" enabled.

Ralph DiMola
IT Director
Evergreen Information Services
rdimola at evergreeninfo.net

-----Original Message-----
From: use-livecode [mailto:use-livecode-bounces at lists.runrev.com] On Behalf
Of Peter TB Brett
Sent: Tuesday, June 07, 2016 11:19 AM
To: How to use LiveCode
Subject: Re: "LiveCode Infinity": lexically-scoped variables and bytecode
blocks

On 07/06/2016 16:04, Dr. Hawkins wrote:
> On Tue, Jun 7, 2016 at 4:05 AM, Peter TB Brett 
> <peter.brett at livecode.com>
> wrote:
>
>> Variables in LCB are going to become lexically scoped ( 
>> https://github.com/livecode/livecode/pull/4113).  This means that 
>> variables declared inside an "if" or "repeat" block won't be 
>> accessible after the end of that block.
>>
>
> To have this in livecode itself is on my top 3 list . . .

Me too!

Unfortunately, as I understand it we can't do this at the moment without
breaking backwards compatibility. :-(

                                     Peter

--
Dr Peter Brett <peter.brett at livecode.com> LiveCode Technical Project Manager

LiveCode 2016 Conference: https://livecode.com/edinburgh-2016/

_______________________________________________
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