constant kMergExtVersion = "2016-6-9"

array (array):

Use the <add> <command> to add a number to a <container> or a portion of a <container>, or to add two <array|arrays> containing numbers.

The contents of the <container> (or the <chunk> of the <container>) must be a number or an <expression> that <evaluate|evaluates> to a number.

If a <number> is added to an <arrayContainer>, the <number> is added to each <element(keyword)>. If an <array> is added to an <arrayContainer>, both <array|arrays> must have the same number of <element(glossary)|elements> and the same dimension, and each <element(keyword)> in the <array> is added to the corresponding <element(keyword)> of the <arrayContainer>.

If the <container> or an <element(keyword)> of the <arrayContainer> is empty, the <add> <command> treats its contents as zero.

If <container> is a <field> or <button>, the <format> of the sum is determined by the <numberFormat> <property>.

References: field (keyword), element (keyword), button (keyword), numberFormat (property), union (command), multiply (command), sum (function), value (function), format (function), property (glossary), element (glossary), container (glossary), expression (glossary), array (glossary), evaluate (glossary), command (glossary)

Example:

-- To create a numbered set of variables with similar names

-- eg myVar1, myVar2, ... myVar20, you can use a repeat loop

-- together with concatenation in the following form. Note that

-- this structure will only work with variable checking

-- turned off.

-- If you prefer to declare your variables then an array is the

-- recommended way of doing this.

local tPrefix = "myVar"

local tVarCount = 20

repeat with tVarNum = 1 to 20

put tPrefix & x into tVarName

do "put empty into " & tVarName

end repeat

array (array): Any existing <container> that contains an <array> of <value|values>.

each time through the loop, rather than the *counter* being increased by

1. (The *increment* is not treated as an absolute value: if you're using

put thisLine comma after newList

if the number of words in thisIndexTerm 1 then

put thisIndexTerm return after multiWordTerms

The ability to specify an increment for the `repeat with `*`counter`*` =

`*`startValue`*` to `*`endValue`* form was added in version 2.0. In

previous versions, this form of the repeat control structure is always

incremented or decremented the counter by 1 each time through the loop.

each key was added in version 2.7.2

Starting in version 7.0 it is possible to modify the *<container>*

variable inside a `for each` loop without affecting the

<iterate|iterations> of the loop.

Summary: Designates a <random|randomly> chosen member of a set.

Use the <any> <keyword> to specify a <random> <object(glossary)> of a specified type, or to designate a <random> <chunk> in a <chunk expression>.

The <any> <keyword> does not examine every member of a set; it specifies just one member of the set, randomly chosen. For example, the expression

if myString is in any field

checks whether myString is in a randomly chosen field, not whether myString is somewhere in one of the fields on the card.

References: first (keyword), random (function), keyword (glossary), random (glossary), chunk expression (glossary), chunk (glossary), object (glossary)

Summary: The <character> <;> is used to place two <statement|statements> on a single <line>.

repeat with x = 1 to 10; doSomething x; end repeat

Use the ; character to compress code into fewer visible lines for easier reading.

Lines that are split with <;> are shown in the <script editor> as a single <line>, but when <execute|executed>, are treated as multiple <lines> of code. The following line counts as three <statement|statements>:

go card 1; beep 2; answer the date

A <;> character which is used within a <literal string> does not signal a new line, because the <;> is treated as part of the <string> instead of being treated as a line break.

References: character (keyword), \ (keyword), line (keyword), string (keyword), lines (keyword), literal string (glossary), statement (glossary), script editor (glossary), execute (glossary)

Description:

Anything between /* and */ is treated as a <comment> and is ignored by LiveCode when <execute|executing> the <handler>.

Comments are useful for documenting and explaining your code, either for others who might need to read and modify it, or for yourself. (The code may be clear in your mind now, but in six months, you'll be glad you included comments.)

The block comments created by </**/> differ from the line <comment|comments> created by -- because a <block comment> can span multiple <lines>, as well as a single <line> or part of a <line>. (A <comment> marked by <--> extends only to the end of the <line>.) A <comment> that starts with /* does not end until */, even if there are several lines in between.

Comments can be placed anywhere in a script--inside handlers or outside all handlers. In a long script with many handlers, it may be useful to divide the handlers into sections. Each section starts with a comment containing the section name and any other useful information. This practice helps you keep long scripts organized. Similarly, a lengthy handler can be made more readable by explanatory comments.

Comments can contain any text, including lines of LiveCode. If the code is within a comment, it's ignored. You can temporarily remove sections of code for debugging by putting those sections inside a comment.

References: lines (keyword), -- (keyword), line (keyword), handler (glossary), comment (glossary), delimit (glossary), block comment (glossary), execute (glossary)