Livecode performance problem

[Mark Wieder]

On 8/19/22 16:03, Bob Sneidar via use-livecode wrote:
> It's probably a lot of text. The engine has to start from the beginning of every string then scan through for every cr or lf or cr/lf or whatever counts as a line break, until if finds the nth one. The more lines, the longer the scan takes each time, and the more text per line the exponentially more time it takes. Multiply that by 4 times plus the combinination of all of them as the code progresses *4 for the output string and you have the makings of a mountain that keeps getting steeper the higher you go.

My tests were based on 2174 lines of text in each field.
Got nowhere near 20 seconds. Or even one.

-- 
  Mark Wieder
  ahsoftware at gmail.com