> On Jun 7, 2016, at 1:37 PM, Dr. Hawkins wrote:
>
> Not being able to exit an
> outer loop (or, for that matter, to identify the companion beginning of a
> control structure, takes odd contortions for the first and several minutes
> at a time for the second.
I like the almost self-referential
What I think we could do which I personally feel would be a bug fix is if a
variable is declared with an initial value then reassign it if we iterate over
the local command again.
For example:
repeat
local tIndex = 1
-- tIndex is always 1 here
repeat
add 1 to tIndex
end
On Tue, Jun 7, 2016 at 11:27 AM, Mike Kerner
wrote:
> I respectfully disagree.
>
It all depends upon what you are doing.
I, by necessity, have layers of nested loops. Not being able to exit an
outer loop (or, for that matter, to identify the companion beginning of a
control structure, takes od
I respectfully disagree.
On Tue, Jun 7, 2016 at 1:27 PM, Dr. Hawkins wrote:
> On Tue, Jun 7, 2016 at 8:51 AM, Peter TB Brett
> wrote:
>
> > Lexically-scoped variables are completely incompatible with the current
> > execution model of LiveCode Script. If you changed it, it would be from
> > ma
In LiveCode, I tend to use small private functions. In a twisted sense, a
handler that calls those does have block-based lexically scoped variables, the
block is just pushed into a separate function.
On those occasions that I do write long handlers (for whatever excuse), I
sometimes pretend
On Tue, Jun 7, 2016 at 8:51 AM, Peter TB Brett
wrote:
> Lexically-scoped variables are completely incompatible with the current
> execution model of LiveCode Script. If you changed it, it would be from
> many perspectives a different language.
>
So are things such as strict compilation, case de
On 07/06/2016 16:43, Ralph DiMola wrote:
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
ices
> rdim...@evergreeninfo.net
>
> -Original Message-
> From: use-livecode [mailto:use-livecode-boun...@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"
ne 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
>
> wrote:
>
>> Variables in LCB are going to become l
On 07/06/2016 16:04, Dr. Hawkins wrote:
On Tue, Jun 7, 2016 at 4:05 AM, Peter TB Brett
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
On Tue, Jun 7, 2016 at 4:05 AM, Peter TB Brett
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 t
On 6/7/2016 7:05 AM, Peter TB Brett wrote:
> The second new feature is the "bytecode" block
> (https://github.com/livecode/livecode/pull/4097). This lets you write
> blocks of raw LCB bytecode in your LCB source files. At the moment
> there are not very many places where this is likely to be usef
Hi folks,
Just a quick update to let you know that work has already started on the
"LiveCode Infinity" improvements to LiveCode Builder.
There are two really interesting things that will be finished soon.
Variables in LCB are going to become lexically scoped
(https://github.com/livecode/live
13 matches
Mail list logo
