File: progress_comments.p

package info (click to toggle)
vim 2%3A9.1.1230-2
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 88,180 kB
  • sloc: ansic: 416,989; cpp: 6,324; makefile: 4,448; java: 2,226; sh: 1,861; perl: 1,419; python: 960; awk: 730; lisp: 501; cs: 458; objc: 369; xml: 247; sed: 8; csh: 6
file content (45 lines) | stat: -rw-r--r-- 1,490 bytes parent folder | download | duplicates (2)
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
45
/*
 * VIM_TEST_SETUP set filetype=progress
 */

define variable customer_name as character no-undo.

/* The test setup above is an example of a multi-line comment.
This is too; the leading * and left-hand alignment are not required. */
for each customer no-lock
    where customer.customer_id = 12345
:
    assign cust_name = customer.customer_name. /* Comments can also appear
                                                  at the end of a line. */
end. /* for each customer */

/* Comments can be /* nested */. Here's the same query as above, but
commented out this time:

for each customer no-lock
    where customer.customer_id = 12345
:
    assign cust_name = customer.customer_name. /* Comments can also appear
                                                  at the end of a line. */
end. /* for each customer */

TODO: Note that /*/ does not end the comment, because it actually starts a
new comment whose first character is a '/'. Now we need two end-comment
markers to return to actual code. */ */

display customer_name.

// This is the single-line comment syntax.

//No space is required after the slashes. Also, a /* here does not begin a
//new block comment.

for each supplier no-lock:
    /* However, a block comment can end inside (what looks like) a
       single-line comment, because the slashes are just text as far as the
       // block comment is concerned. */
    display supplier.

    // TODO: Observe that todo highlighting works in line comments too.
end.