This repository was archived by the owner on Aug 31, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 225
Expand file tree
/
Copy pathdashdash.lcdoc
More file actions
45 lines (30 loc) · 1.32 KB
/
dashdash.lcdoc
File metadata and controls
45 lines (30 loc) · 1.32 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
Name: --
Synonyms: #
Type: keyword
Syntax: --
Summary:
Indicates the start of a <comment>.
Introduced: 1.0
OS: mac, windows, linux, ios, android
Platforms: desktop, server, mobile
Example:
myVar -- myVar holds the index
Example:
-- everything on this line is a comment
Description:
Anything between -- and the end of the current script line is treated as
a comment and is ignored by LiveCode when 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.)
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: comment (glossary), /**/ (keyword), - (operator)