Cubist's first bug report

[Lagi Pittas]

Hi

Just read further back through the thread and looks like Monte has a handle
on it

I’ve taken a little look into it and yes it does appear the chunk is being
> evaluated twice: Add left to right
> - get value to add by and evaluate chunk if any
> - get destination value and evaluate chunk if any
> - add
> - set destination value and evaluate chunk if any So I think we can both
> fix this quirk and optimise things that mutate rather than replace the
> destination chunk (add, subtract, multiply, divide commands… are there
> others?) by setting the previously marked chunk rather than re-evaluating.
> Please submit a bug report so we can look into it further and work out
> whether I’m right or I just don’t know my way around the engine well enough
> yet ;-) Cheers Monte


Lagi

On 6 June 2016 at 05:34, FlexibleLearning.com <admin at flexiblelearning.com>
wrote:

> This double-evaluation bug has existed since MC v4.2 (the earliest engine I
> have immediately to hand).
>
> [snip]
> on mouseUp
>    put "1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16" into myVar
>    repeat 1000
>       add zero to any item of myVar
>    end repeat
>    put  myVar
> end mouseUp
> [/snip]
>
> Hugh Senior
> FLCo
>
>
>
> _______________________________________________
> 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
>